But I would not expect any manual edits of the DaemonSet to persist. cdk-addons will generally revert any changes you made within 5 minutes. To override the deployed version in a persistent way, I think you would have to remove the relation between kubernetes-control-plane and openstack-integrator, then deploy OCCM yourself.
In case it's helpful to you, I've synced the following images to rocks:
rocks.canonical .com/cdk/ k8scloudprovide r/openstack- cloud-controlle r-manager: v1.25.3 .com/cdk/ k8scloudprovide r/openstack- cloud-controlle r-manager: v1.25.4 .com/cdk/ k8scloudprovide r/openstack- cloud-controlle r-manager: v1.26.0 .com/cdk/ k8scloudprovide r/openstack- cloud-controlle r-manager: v1.26.1
rocks.canonical
rocks.canonical
rocks.canonical
But I would not expect any manual edits of the DaemonSet to persist. cdk-addons will generally revert any changes you made within 5 minutes. To override the deployed version in a persistent way, I think you would have to remove the relation between kubernetes- control- plane and openstack- integrator, then deploy OCCM yourself.