operator-sdk generate kustomize manifests

operator-sdk generate kustomize manifests

Generates kustomize bases and a kustomization.yaml for operator-framework manifests

Synopsis

Running ‘generate kustomize manifests’ will (re)generate kustomize bases and a kustomization.yaml in ‘config/manifests’, which are used to build operator-framework manifests by other operator-sdk commands. This command will interactively ask for UI metadata, an important component of manifest bases, by default unless a base already exists or you set ‘–interactive=false’.

  1. operator-sdk generate kustomize manifests [flags]

Examples

  1. $ operator-sdk generate kustomize manifests
  2. Display name for the operator (required):
  3. > memcached-operator
  4. ...
  5. $ tree config/manifests
  6. config/manifests
  7. ├── bases
  8. └── memcached-operator.clusterserviceversion.yaml
  9. └── kustomization.yaml
  10. # After generating kustomize bases and a kustomization.yaml, you can generate a bundle or package manifests.
  11. # To generate a bundle:
  12. $ kustomize build config/manifests | operator-sdk generate bundle --version 0.0.1
  13. # To generate package manifests:
  14. $ kustomize build config/manifests | operator-sdk generate packagemanifests --version 0.0.1

Options

  1. --apis-dir string Root directory for API type defintions
  2. -h, --help help for manifests
  3. --input-dir string Directory containing existing kustomize files
  4. --interactive When set or no kustomize base exists, an interactive command prompt will be presented to accept non-inferrable metadata
  5. --output-dir string Directory to write kustomize files
  6. -q, --quiet Run in quiet mode

Options inherited from parent commands

  1. --verbose Enable verbose logging

SEE ALSO

Last modified July 29, 2020: generate: remove `—operator-name` (#3530) (bbc2f254)