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
Is your feature request related to a problem? Please describe.
We are still running Kubernetes version 1.25.5 and PhotonOS 4.0 Rev.2 in VEBA. The Tanzu Sources for Knative v.0.39.0 already requires k8s version 1.26 as a minimum. Running an older k8s version with v.0.39.0 of the Sources will result in an error:
k -n vmware-sources logs vsphere-source-webhook-64c58bc7d9-cn5qs
{"level":"fatal","ts":"2023-12-27T10:45:02.484Z","logger":"vsphere-source-webhook","caller":"sharedmain/main.go:386","msg":"Version check failed","commit":"536930e-dirty","error":"kubernetes version \"1.25.5\" is not compatible, need at least \"1.26.0-0\" (this can be overridden with the env var \"KUBERNETES_MIN_VERSION\")","stacktrace":"knative.dev/pkg/injection/sharedmain.CheckK8sClientMinimumVersionOrDie\n\tknative.dev/pkg@v0.0.0-20231211072236-4914c472e81a/injection/sharedmain/main.go:386\nknative.dev/pkg/injection/sharedmain.MainWithConfig\n\tknative.dev/pkg@v0.0.0-20231211072236-4914c472e81a/injection/sharedmain/main.go:256\nknative.dev/pkg/injection/sharedmain.MainWithContext\n\tknative.dev/pkg@v0.0.0-20231211072236-4914c472e81a/injection/sharedmain/main.go:210\nmain.main\n\tgit.luolix.top/vmware-tanzu/sources-for-knative/cmd/vsphere-controller/main.go:143\nruntime.main\n\truntime/proc.go:267"}
I've validated the suggested workaround successfully but we have to bump all components in VEBA to a newer version.
Is your feature request related to a problem? Please describe.
We are still running Kubernetes version 1.25.5 and PhotonOS 4.0 Rev.2 in VEBA. The Tanzu Sources for Knative v.0.39.0 already requires k8s version 1.26 as a minimum. Running an older k8s version with v.0.39.0 of the Sources will result in an error:
I've validated the suggested workaround successfully but we have to bump all components in VEBA to a newer version.
Workaround:
The text was updated successfully, but these errors were encountered: