For operational maintenance and introspection, airlock should grow some CLI subcommands.
Those are mostly meant for human consumption, in order to inspect state in etcd3 and act on it.
The idea is that the administrator can kubectl exec into the container and run maintenance commands there. Those commands requires access to the configuration, which is already available inside the container.
Here below is an initial list of tasks I'd like to be able to perform via CLI.
For operational maintenance and introspection, airlock should grow some CLI subcommands.
Those are mostly meant for human consumption, in order to inspect state in etcd3 and act on it.
The idea is that the administrator can
kubectl execinto the container and run maintenance commands there. Those commands requires access to the configuration, which is already available inside the container.Here below is an initial list of tasks I'd like to be able to perform via CLI.