Ability to override docker images

Bug #1814332 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tigera Secure EE Charm
Fix Released
Wishlist
Unassigned

Bug Description

Originally brought up here: https://github.com/juju-solutions/layer-tigera-secure-ee/pull/5

In the Calico charm, it was possible to bring your own calicoctl resource and configure exact docker images for calico-node and calico-kube-controllers. It's not possible to do the same with the Tigera Secure EE charm.

The main use case, which is to specify a different docker registry, is still supported via the registry config.

One use case that is not supported is testing a new release of Tigera Secure EE without having to release a new charm.

George Kraft (cynerva)
description: updated
description: updated
Revision history for this message
Joseph Borg (joeborg) wrote :
Revision history for this message
George Kraft (cynerva) wrote :

Yeah, looks like it. Thanks.

Fixed with https://github.com/charmed-kubernetes/layer-tigera-secure-ee/pull/15

Release to stable with cs:~containers/tigera-secure-ee-55

Changed in charm-tigera-secure-ee:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.