vpctl secret commands
Generate and deploy Kubernetes Secret manifests from a secrets.import.yaml input
Read time 1 minuteLast updated a day ago
Use the
secretSecretGenerate secrets
Create Kubernetes secret YAML files from your secret definitions. For the import file format, refer tosecrets.import.example.yamlParameters:vpctl secret generate --import secrets.import.yaml --use-defaults
- : Path to the secrets import file. See
--importfor the format.secrets.import.example.yaml - : Use default values or auto-generate values without prompts (non-interactive mode). If a required field has no default or auto-generate option, the tool writes
--use-defaultsand logs a warning so you can update it before deployment.TBD - : Output file path (defaults to
--output).secrets.yaml - : Generate only the specified secret by name.
--name - : Path to the extracted release directory (defaults to
--extracted-release)../extracted-release - : Clear the output file before generating (default: false).
--clean-output - : Skip the vpctl version compatibility check against the release package.
--skip-version-check - : Save generated values to an import-format file for reuse in subsequent runs. Pass without a value to use the default
--persist [path], or specify a custom path. On later runs, the tool loads the persisted file and reuses existing values without regenerating them.secrets.import.yaml
vpctl secret generate --import secrets.import.yaml --use-defaults --output ./generated-secrets.yaml
Deploy secrets to Kubernetes
Apply the generated secrets to your Kubernetes cluster:Common options:vpctl secret deploy
- : Path to the secrets YAML file (defaults to
--file).secrets.yaml - : Preview the kubectl command without executing it.
--dry-run - : Kubernetes context to use.
--context - : Kubernetes namespace (overrides the namespace in the secret YAML).
--namespace
vpctl secret deploy --file ./generated-secrets.yaml --namespace production --dry-run