operator-sdk generate bundle

operator-sdk generate bundle

Generates bundle data for the operator

Synopsis

Generates bundle data for the operator

  1. operator-sdk generate bundle [flags]

Options

  1. --apis-dir string Root directory for API type defintions
  2. --channels string A comma-separated list of channels the bundle belongs to (default "alpha")
  3. --crds-dir string Root directory for CustomResoureDefinition manifests
  4. --default-channel string The default channel for the bundle
  5. -h, --help help for bundle
  6. --input-dir string Directory to read an existing bundle from. This directory is the parent of your bundle 'manifests' directory, and different from --manifest-root
  7. --interactive When set or no bundle base exists, an interactive command prompt will be presented to accept bundle ClusterServiceVersion metadata
  8. --manifests Generate bundle manifests
  9. --metadata Generate bundle metadata and Dockerfile
  10. --operator-name string Name of the bundle's operator
  11. --output-dir string Directory to write the bundle to
  12. --overwrite Overwrite the bundle's metadata and Dockerfile if they exist
  13. -q, --quiet Run in quiet mode
  14. -v, --version string Semantic version of the operator in the generated bundle. Only set if creating a new bundle or upgrading your operator

SEE ALSO

Last modified May 22, 2020: generate: add `bundle` subcommand for current project layouts (#3088) (6c48dc2a)