-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tigera-operator docs for EKS contains deprecated API versions #6491
Comments
I tried to run
|
|
Apparently, it wasn't the solution, because after it finished progressing and rebooted all the pods in calico-system tigerastatus looked like this:
Few seconds after, the pods started to reboot again and that was the tigerastatus output:
The logs from from the tigera-operator namespace:
|
Yes, we need to update the EKS documentation to use a newer version. Did you install via helm originally? |
@caseydavenport
But in order to upgrade it, since I didn't use helm in the first place, I used the command:
EDIT: Installing tigera-operator via helm created the apiserver in tigerastatus and solved the errors of "APIServer config not found", but PodSecurityPolicy resources are still being deployed. |
PodSecurityPolicy has been removed in master and the upcoming v3.24 release:
Once v3.24 is out, we just need to update the EKS documentation. |
This is deliberate. By continuing to use deprecated k8s APIs, we can ensure that the compatibility of Calico with multiple versions of k8s. (arguably this is the point of deprecation) We typically switch to the new API just before the removal of the API from k8s - e.g. in this case Calico v3.24 was the last Calico release before k8s 1.25 came out and removed this API, so that is the release we switched from PodSecurityPolicies to PodSecurityStandards. |
v3.24 is out now, so we're clear to update the docs. I believe @coutinhop was looking at making some changes in that area already? |
I still get |
@viceice use |
We need to figure out if there's a way we can avoid this situation, but in general |
@caseydavenport Thanks! |
Closing this as using |
Still issue but in ArgoCD. I created application tigera-operator and faced with the same issue. ArgoCD application manifset:
|
I'm upgrading EKS from 1.21 to the 1.22 version. PodSecurityPolicy in the policy/v1beta1 API version is being deprecated in Kubernetes 1.21 and will no longer be served in v1.25. I followed the documentation here for the operator installation but the instructions aren't updated for newer Kubernetes versions which cannot deploy PodSecurityPolicy (1.22+).
Expected Behavior
Installing Calico using tigera-operator.yaml from the documentation should be compatible with newer Kubernetes versions as it is for the calico installation from manifest
Current Behavior
tigera-operator installation as mentioned in the EKS documentation of project calico installs old API versions which are deprecated in k8s v1.22+
Your Environment
The text was updated successfully, but these errors were encountered: