Custom init container
Creating a custom init container is a more advanced topic for kubernetes users. An init container is designed to run before starting the main container.
Potential use for custom init container:
-
Debug/patch container storage
-
Custom container to load data spaces
-
Perform any operation on the container/pod prior to starting the container
To use a customer init container, use the following helm parameter override
values:
onedb:
customInitImage: gcr.io/google-containers/busybox:latest
customInitImageCmd: /bin/customization.sh
If you needed to login to this container, the name of the init container is onedb-custom-init, although we could use the kubectl describe pod command to determine this.