![]() ![]() Note: For more details and examples run operator-sdk init -plugins helm -help. The option -helm-chart-version is not used when -helm-chart itself refers to a specific version, for example when it is a local path or a URL. Otherwise, it will fetch the specified version. If -helm-chart-version is not set, the SDK will fetch the latest available version of the helm chart. : Fetch the helm chart named chartName in the helm chart repository.If a custom repository URL is specified by -helm-chart-repo, the only supported format for -helm-chart is: : Fetch the helm chart archive at the specified URL. Use helm repo add to configure this file. $HELM_HOME/repositories/repositories.yaml file. : Fetch the helm chart named chartName from the helmĬhart repository named repoName, as specified in the If a custom repository URL is not specified by -helm-chart-repo, the following chart reference formats are supported: ![]() Otherwise, the SDK will attempt to fetch the specified helm chart from a remote repository. It will be validated and unpacked or copied into the project. If -helm-chart is a local chart archive (e.g example-chart-1.2.0.tgz) or directory, If -helm-chart is specified, the -group, -version, and -kind flags become optional. Instead of creating your project with a boilerplate Helm chart, you can also use -helm-chart, -helm-chart-repo, and -helm-chart-version to use an existing chart, either from your local filesystem or a remote chart repository. To learn more about the project directory structure, see the In config/rbac/role.yaml meet the operator’s permission requirements. ![]() Be sure to double check that the rules generated In config/rbac/role.yaml based on the resources that would be deployed by theĬhart’s default manifest. Nginx resource with APIVersion /v1alpha1 and Kindįor Helm-based projects, operator-sdk init also generates the RBAC rules This creates the nginx-operator project specifically for watching the Operator-sdk init -plugins helm -domain -group demo -version v1alpha1 -kind Nginx ![]()
0 Comments
Leave a Reply. |