I've re-targeted this to cdk-addons 1.27 for now, which would go out with Charmed Kubernetes 1.27 by April 18th.
The feedback we've received is that updating image versions in a cdk-addons point release is very disruptive to offline deployments, so it's something that we would prefer not to do. That said, if you need this fixed in a 1.26 release, let us know and we will consider it.
I've re-targeted this to cdk-addons 1.27 for now, which would go out with Charmed Kubernetes 1.27 by April 18th.
The feedback we've received is that updating image versions in a cdk-addons point release is very disruptive to offline deployments, so it's something that we would prefer not to do. That said, if you need this fixed in a 1.26 release, let us know and we will consider it.