Prevent updating Tyk regardless of changes in each reconciliation

[buraksekili]

Description

Users raised possible performance issues in the reconciliation cycle of Tyk Operator. While reconciling a large amount of resources, Operator makes redundant external API calls to Tyk Gateway / Dashboard. This PR compares hashes of an existing resource and an updated resource and prevents calling Update API of GW/Dashboard if no changes are made.

Related Issue

https://tyktech.atlassian.net/browse/TT-7610

Motivation and Context

By default, Operator triggers reconciliation in 10hrs approximately. So, if you have a large number of resources in your cluster, Operator tries to reconcile each of your resources in the cluster even though you haven't changed anything. With the current flow, Operator sends Update requests to Tyk Gateway / Dashboard regardless of changes in resources. This causes issues if your GW is running under certain resource limitations.

Test Coverage For This Change

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If PRing from your fork, don't come from your master!
• Make sure you are making a pull request against our master branch (left side). Also, it would be best if you started your change off our latest master.
• Make sure you are updating CHANGELOG.md based on your changes.
• My change requires a change to the documentation.
  • If you've changed APIs, describe what needs to be updated in the documentation.
• I have updated the documentation accordingly.
• If you've changed API models, please update CRDs.
  • make manifests
  • make helm
• I have added tests to cover my changes.
• All new and existing tests passed.
• Check your code additions will not fail linting checks:
  • gofmt -s -w .
  • go vet ./...
  • golangci-lint run

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

9.8% Coverage
0.0% Duplication