I have the docker container image for the ignition from inductive automation and in the docker local the volume works at expected but in kubernetes it doesn't work as expected because only the modules are the ones that are not persisting and i want to know if im doing something wrong and i want to read some documentation or something like that
If you search this forum for "ignition kubernetes", this is in the results:
The link above is a good starting point to understand some of the conventions you need to align to for deploying Ignition in K8s. We are working on a Helm chart to make K8s deployments easier (abstracting away a good amount of complexity). Stay tuned!
In the meantime, for the current version of Ignition (8.1.x), you'll need to do one of a couple things at the moment to persist third-party modules:
- Build and use a derived image that bundles in those modules. See my ignition-derived-example for some examples there.
- Copy in the module at time-of-launch. There are a few ways to go about this; the easiest would be to add an entrypoint shim that copies the module into the container before launching Ignition (since this particular operation can't be done in an initContainer).
EDIT: If you're wanting to adjust the set of built-in modules, use the GATEWAY_MODULES_ENABLED
environment variable.
Interesting it would be nice if can i have an example for the 'Copy in the module at time-of-launch' entrypoint with the yaml to test it, but im lookin in to the ignition-derived-example, because right now im trying to persist the azure injector module, thank you in advance.