-
Notifications
You must be signed in to change notification settings - Fork 188
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
operatorhub.io still thinks the latest version of the tekton operator is 0.61. #1493
Comments
@RobVerduijn thanks to report this issue. |
Hi, Another release of tekton was done last week, however this has not been published on operatorhub.io Please make publishing the release on operatorhub.io part of your pipeline. |
Its been a few months, any updates on this? 0.61 is still the latest release posted there. Not sure if this is aimed to be fixed in the next release. |
Should I believe the operator is no longer maintained as far as releases to operatorhub.io? What is the recommended installation method? I am using ArgoCD and GitOps |
Bumping this as a more pressing issue. The current version of the operator on Operatorhub.io uses HPA |
Update KinD to latest released version (v0.20.0) and use the supported v1.24 k8s node version from the corresponding release note. The current Tekton operator on OperatorHub does not support k8s 1.25 or higher. This also sets the minKubeVersion to 1.24.0 on the operator CSV so the version we test with and the min supported version are aligned. See tektoncd/operator#1493.
Update KinD to latest released version (v0.20.0) and use the supported v1.24 k8s node version from the corresponding release note. The current Tekton operator on OperatorHub does not support k8s 1.25 or higher. This also sets the minKubeVersion to 1.24.0 on the operator CSV so the version we test with and the min supported version are aligned. See tektoncd/operator#1493.
When trying to install the tekton operator on okd using the operatorhub.io it installs version 0.61
there are 2 yaml files below
edit: no more error, this was due to the use of the wrong image in the catalogue definition
packagemanifest tektoncd-operator:
catalogsource:
The text was updated successfully, but these errors were encountered: