We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We found that occm 1.28.0 was installed regardless of the k8s version or cloud_provider_tag.
cloud_provider_tag
There is code here to search/replace in the desired version of occm
magnum-cluster-api/magnum_cluster_api/resources.py
Lines 225 to 226 in 7044ba8
Here is the manifest it wants to patch
magnum-cluster-api/magnum_cluster_api/manifests/ccm/openstack-cloud-controller-manager-ds.yaml
Line 37 in 7044ba8
I think that commit cae70f7 adjusted the manifest in a way that the search/replace no longer matches, so the version in the manifest is always used.
This results in inability to use the expected features in a workload cluster, in our case [KEP-1860] which was introduced in 1.30.0.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We found that occm 1.28.0 was installed regardless of the k8s version or
cloud_provider_tag
.There is code here to search/replace in the desired version of occm
magnum-cluster-api/magnum_cluster_api/resources.py
Lines 225 to 226 in 7044ba8
Here is the manifest it wants to patch
magnum-cluster-api/magnum_cluster_api/manifests/ccm/openstack-cloud-controller-manager-ds.yaml
Line 37 in 7044ba8
I think that commit cae70f7 adjusted the manifest in a way that the search/replace no longer matches, so the version in the manifest is always used.
This results in inability to use the expected features in a workload cluster, in our case [KEP-1860] which was introduced in 1.30.0.
The text was updated successfully, but these errors were encountered: