[feature] add ability to specify a private registry to pull required e2e images from
Bug #1837095 reported by
Jeff Hillman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Kubernetes E2E Test Charm |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
There is currently no way to specify a private registry to pull the required e2e test images from.
Effectively, this means that in an "offline", "isolated", or "air-gapped" environment, the kubernetes-e2e charm cannot be run and an environment cannot be evaluated in this manner.
If there could be a charm config option to specify this, similar to how kubernetes-master has the ability to specify the addons-registry, we could then pull from a private (onsite) registry.
Revision history for this message
| George Kraft (cynerva) wrote | #1 |
| Changed in charm-kubernetes-e2e: | |
| status: | New → Confirmed |
| Changed in charm-kubernetes-e2e: | |
| importance: | Undecided → Wishlist |
| status: | Confirmed → Triaged |
To post a comment you must log in.
Indeed, the kubernetes-e2e charm does not currently support this case.
Upstream Kubernetes E2E makes this possible with the undocumented KUBE_TEST_REPO_LIST environment variable: https:/
The charm would most likely need to utilize KUBE_TEST_REPO_LIST to support this.