operator-sdk run packagemanifests
operator-sdk run packagemanifests
Deploy an Operator in the package manifests format with OLM
Synopsis
‘run packagemanifests’ deploys an Operator’s package manifests with OLM. The command’s argument must be set to a valid package manifests root directory, ex. ‘/packagemanifests’.
operator-sdk run packagemanifests [flags]
Options
-h, --help help for packagemanifests
--include strings Path to Kubernetes resource manifests, ex. Role, Subscription. These supplement or override defaults generated by run/cleanup
--install-mode string InstallMode to create OperatorGroup with. Format: InstallModeType[=ns1,ns2[, ...]]
--kubeconfig string The file path to kubernetes configuration file. Defaults to location specified by $KUBECONFIG, or to default file rules if not set
--olm-namespace string The namespace where OLM is installed (default "olm")
--operator-namespace string The namespace where operator resources are created. It must already exist in the cluster or be defined in a manifest passed to --include
--operator-version string Version of operator to deploy
--timeout duration Time to wait for the command to complete before failing (default 2m0s)
SEE ALSO
- operator-sdk run - Run an Operator in a variety of environments
Last modified June 30, 2020: cli (new): add `run packagemanifests` (#3253) (cb8bf474)
当前内容版权归 operatorframework 或其关联方所有,如需对内容或内容相关联开源项目进行关注与资助,请访问 operatorframework .