Deprecate custom-registry-ca option
Bug #1898870 reported by
Chris Johnston
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Container Runtime Common Layer |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Since the ability to specify a ca for each custom registry now exists we should deprecate the "global" custom-registry-ca option.
| Changed in charm-containerd: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Kevin W Monroe (kwmonroe) wrote | #1 |
| affects: | charm-containerd → layer-container-runtime-common |
To post a comment you must log in.
Re-targeting since this global option lives in the common container layer:
https:/
So we'd need to check the impact for docker as well.