validate containerd config

Bug #1881173 reported by Kevin W Monroe
10
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://github.com/charmed-kubernetes/charm-containerd/pull/39, one example of something we need to validate is that 'ca|cert|key_file' values are b64 encoded. Another would be that each registry item has a 'url' key/value.

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
George Kraft (cynerva)
Changed in charm-containerd:
status: New → Triaged
Adam Dyess (addyess)
Changed in charm-containerd:
assignee: nobody → Adam Dyess (addyess)
Adam Dyess (addyess)
Changed in charm-containerd:
status: Triaged → In Progress
Revision history for this message
Adam Dyess (addyess) wrote :
George Kraft (cynerva)
Changed in charm-containerd:
status: In Progress → Fix Committed
milestone: none → 1.23
George Kraft (cynerva)
Changed in charm-containerd:
status: Fix Committed → 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.