Any secret that is created here should have it's counterpart in Vault by the same name. Otomi will create kubernetes secrets from those Vault secrets. These can then be used in Otomi Services and Otomi Jobs, as injected env vars, or as file mounts.
Otomi supports 3 types of secrets:
Create a generic kubernetes secret by listing a selection of (or all) properties of a Vault secret registered with the same name.
The docker registry (or pull) secret should exist in Vault as a secret with the same name. The vault secret should be of type "json" and have only one property
.dockerconfigjson. Use the following command to create the json:
To create a TLS secret, the fields should correspond with the properties as named in the Vault secret registered with the same name. The "ca" field is optional and can be used to provide the certificate authority (for mTLS).
|crt||The property name pointing to the PEM encoded public key certificate in Vault||tls.crt|
|key||The property name pointing to the private key certificate content in Vault||tls.key|
|ca||The property name pointing to the CA certificate content in Vault (optional)||ca.crt|