feat: Make the Kube-OVN install script check version match with overr… #978
Conversation
|
I found install-kube-ovn.sh installing chart version v1.12.31 with image v1.12.32 from /opt/genestack/base-helm-configs/kube-ovn/kube-ovn-helm-overrides.yaml |
…ide image JIRA:OSPC-1243
awfabian-rs
force-pushed
the
install-kube-ovn-image-version
branch
from
2fed9e9 to
b6f42d8
Compare
| @@ -10,7 +10,7 @@ global: | |||
| repository: kube-ovn | |||
| dpdkRepository: kube-ovn-dpdk | |||
| vpcRepository: vpc-nat-gateway | |||
| tag: v1.12.32 | |||
| tag: v1.12.31 | |||
There was a problem hiding this comment.
The image we have right now is set to 1.12.32 via https://github.com/rackerlabs/kube-ovn/pkgs/container/kube-ovn/361087350?tag=v1.12.32 - however, I think we could repoint the registry adress back upstream to a more up to date release at this point.
There was a problem hiding this comment.
@cloudnull Running helm repo update and helm search repo kubeovn/kube-ovn --versions on the dfw dev overseer shows the latest v1.12.x chart as v1.12.31. I don't know if we want to allow version mismatch between the chart installed version and the image version, as image v1.12.32 probably works fine with chart v1.12.31, and it appears the chart might have a slight release lag? I think we have to use chart v1.12.31
Or perhaps we would want to table this until a v1.12.32 chart appears or we switch to a v1.13.x?
There was a problem hiding this comment.
Lets update main to v1.13.x within this PR, I think it makes sense to keep the version in sync like you're aiming for and I think it makes sense to do it within the curent stable kube-ovn.
…ide image
JIRA:OSPC-1243