Clean install issue #7998
Comments
|
Most of the test we did were on 1.21, I will spin up a local cluster, and create fixes to make it work with 1.22 this weekend. |
|
I have got the issue replicated in a local cluster. I guess this is related to https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/ . I am hoping this would be ok if I switch back to 1.21 🤞 . |
Yes 🤞 |
|
Do you work on upgrade for resolve problem with 1.22. Or better downgrade to 1.21? |
|
With 1.23 out,it would be good to fix this for 1.22. So for local testing, I use k3s (and in my company I use AWS), and the stable channel still does not have 1.22 (they are on 1.21.7 last time I checked and AWS still does not have 1.22). I could use the latest channel of k3s which has 1.22.4, but there might be issues with k3s which might make debugging JX issues harder, but I will give it a shot, if stable k3s channel does not have a 1.22 release by Dec 17. Once I can get a 1.22 cluster on k3s, I will check what needs to be done to fix it. |
|
Perhaps update the documentation on k3s (https://jenkins-x.io/v3/admin/platforms/k3s/) to mention it's compatible with only version 1.21 at the moment? |
|
Jenkins X as a whole is not compatible with 1.22 yet, we still use the beta apis for crds. |
Hi |
|
Yes, I have a PR re-generating crds to work with kubernetes 1.22: jenkins-x/jx-api#162. Once that is done (need to re-generate open api validation schema) and merged, the last issue is upgrading tekton, and seeing if it works. |
|
If anyone wants to try, and give us some feedback, then the manifests are in this PR: jenkins-x-charts/jenkins-x-crds#8 (you can try my fork with branch - Is any one running kubernetes 1.21, and wants to try it, that would also be nice! We dont want to break existing clusters ... |
|
#8032 -> Issue tracking kuberntes 1.22 support. |
|
do we have an update on when it is going to be compatible with 1.22? i have the same issue deploying the operator and downgrading is not an option at the moment |
|
https://github.com/jenkins-x-charts/jenkins-x-crds/releases/tag/v3.0.12 -> Use version 3.0.12 for crds (it got merged today, but not yet available in the version stream). Change here to 3.0.12: https://github.com/DexaiRobotics/jx3-eks-vault/blob/bbceb058a4a7b5afcf21f3aea1d50d623719cdc5/versionStream/charts/jxgh/jx-build-controller/defaults.yaml#L2 The only other PR that remains is: cdfoundation/tekton-helm-chart#17. which should get merged soon. |
Can you please create a more step by step explanation of what is needed to be done in order to deploy jenkinsx in kubernetes 1.22? I cannot follow up on some of the instructions provided |
|
Closing this issue as we have other issues covering kubernetes 1.22 upgrade #8032 |
Hello, i use clean instance Kubernetes v1.22 with jx v3.2.213
With this guide
https://jenkins-x.io/v3/admin/platforms/on-premises/
i have error on add git operator stage:
in k8s failed started job jx-boot:3.2.213
The text was updated successfully, but these errors were encountered: