validate containerd config
Bug #1881173 reported by
Kevin W Monroe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Containerd Subordinate Charm |
Fix Released
|
Wishlist
|
Adam Dyess |
Bug Description
The 'custom_registries' config option is a json array posing as a string. This is prone to error, so we should validate that the data contains the fields and data types that we expect.
Initially discussed in https:/
If we come across bad data in the config, the charm should block until the operator sets valid config.
Changed in charm-containerd: | |
importance: | Undecided → Wishlist |
description: | updated |
Changed in charm-containerd: | |
status: | New → Triaged |
Changed in charm-containerd: | |
assignee: | nobody → Adam Dyess (addyess) |
Changed in charm-containerd: | |
status: | Triaged → In Progress |
Changed in charm-containerd: | |
status: | In Progress → Fix Committed |
milestone: | none → 1.23 |
Changed in charm-containerd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Raised PR to address: /github. com/charmed- kubernetes/ charm-container d/pull/ 57/
https:/