operator-sdk run bundle

operator-sdk run bundle

Deploy an Operator in the bundle format with OLM

Synopsis

The single argument to this command is a bundle image, with the full registry path specified. If using a docker.io image, you must specify docker.io(/<namespace>)?/<bundle-image-name>:<tag>.

  1. operator-sdk run bundle <bundle-image> [flags]

Options

  1. --ca-secret-name string Name of a generic secret containing a PEM root certificate file required to pull bundle images. This secret *must* be in the namespace that this command is configured to run in, and the file *must* be encoded under the key "cert.pem"
  2. -h, --help help for bundle
  3. --index-image string index image in which to inject bundle (default "quay.io/operator-framework/opm:latest")
  4. --install-mode InstallModeValue install mode
  5. --kubeconfig string Path to the kubeconfig file to use for CLI requests.
  6. -n, --namespace string If present, namespace scope for this CLI request
  7. --pull-secret-name string Name of image pull secret ("type: kubernetes.io/dockerconfigjson") required to pull bundle images. This secret *must* be both in the namespace and an imagePullSecret of the service account that this command is configured to run in
  8. --service-account string Service account name to bind registry objects to. If unset, the default service account is used. This value does not override the operator's service account
  9. --skip-tls skip authentication of image registry TLS certificate when pulling a bundle image in-cluster
  10. --timeout duration Duration to wait for the command to complete before failing (default 2m0s)

Options inherited from parent commands

  1. --plugins strings plugin keys to be used for this subcommand execution
  2. --verbose Enable verbose logging

SEE ALSO

Last modified September 20, 2021: update default opm index image for run bundle (#5171) (4ae30332)