© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
I think we can find a nice way to truncate image prefixes, but we would then expect all images to be in a flat structure at the configured image-registry.
That may cover a majority of private registry users, but I think we'll have some that want certain images (maybe storage-related) to come from a ./k8s-storage prefix and others (maybe ingress) to come from a ./k8s-ingress prefix. That scenario would be more difficult to accommodate -- the only solution I have for that today would be to expose config for every image that could possibly be used in a CDK deploy, and that's a mess.
Thanks for the bug report; it's certainly something we'll hash out.