chore(AutoDiscoverProvider): implements conflicts discovery #2201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I recently went through a scenario where using an RKE2 cluster it was necessary to create the
GKEBackendConfig
to maintain compatibility during the migration of some services. Because of this, thenetworking.gke.io/v1
group was created in the cluster and this caused the tigera/operator to erroneously infer thekubernetesProvider
field and lead us to a failure scenario.Considering this scenario and other similar ones, this MR implements the detection of conflicts during the inference of the Kubernetes Provider, generating an error if more than one provider is detected.
For PR author
make gen-files
make gen-versions
For PR reviewers
A note for code reviewers - all pull requests must have the following:
kind/bug
if this is a bugfix.kind/enhancement
if this is a a new feature.enterprise
if this PR applies to Calico Enterprise only.