You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code in pkg/controller/utils/discovery.go in the function autodetectFromGroup results in wrong results.
We run tigera-operater on EKS and the installation uses: kubernetesProvider: EKS but we observed the following error:
Installation spec.kubernetesProvider 'EKS' does not match auto-detected value 'GKE'
We found out that the code
ifg.Name=="networking.gke.io" {
// Running on GKE.returnoperatorv1.ProviderGKE, nil
}
is responsible for our Problem. We are using fqdnnetworkpolicies in the group networking.gke.io and therefore autodetectFromGroup results in the wrong value.
Expected Behavior
Tigera Operator should detect the correct cluster type
Current Behavior
tigera-operator blives to be in GKE and complains about the kubernetesProvider: EKS setting in the installation
Possible Solution
Allow to disable AutoDiscoverProvider by using a ENV variable or a argument for the operator
Steps to Reproduce (for bugs)
install fqdnnetworkpolicies.networking.gke.io on a EKS cluster
start tigera-operator
Context
Your Environment
Operating System and version:
Link to your project (optional):
The text was updated successfully, but these errors were encountered:
akesser
changed the title
AutoDiscoverProvider lead to wrong result
AutoDiscoverProvider leads to wrong result
Oct 10, 2023
The code in pkg/controller/utils/discovery.go in the function
autodetectFromGroup
results in wrong results.We run tigera-operater on EKS and the installation uses:
kubernetesProvider: EKS
but we observed the following error:We found out that the code
is responsible for our Problem. We are using
fqdnnetworkpolicies
in the groupnetworking.gke.io
and thereforeautodetectFromGroup
results in the wrong value.Expected Behavior
Tigera Operator should detect the correct cluster type
Current Behavior
tigera-operator blives to be in GKE and complains about the
kubernetesProvider: EKS
setting in the installationPossible Solution
Allow to disable
AutoDiscoverProvider
by using a ENV variable or a argument for the operatorSteps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: