It is also possible to deploy Helm charts as AddOns. AddOns are created automatically by the deploy controller, and are named based on their filename in the manifests directory. You will find AddOns for packaged components such as CoreDNS, Local-Storage, Traefik, etc. Manifests deployed in this manner are managed as AddOn custom resources, and can be viewed by running kubectl get addon -A. Customizing Packaged Components with HelmChartConfigĪutomatically Deploying Manifests and Helm ChartsĪny Kubernetes manifests found in /var/lib/rancher/k3s/server/manifests will automatically be deployed to K3s in a manner similar to kubectl apply.
Automatically Deploying Manifests and Helm Charts.This section covers the following topics: K3s does include some extra functionality to make deploying both traditional Kubernetes resource manifests and Helm Charts even easier with the rancher/helm-release CRD. Just be sure you have properly set up your kubeconfig as per the section about cluster access. K3s does not require any special configuration to use with Helm command-line tools. For more information about creating your own catalog of deployments, check out the docs at. With Helm we can create configurable deployments instead of just using static files. Helm charts provide templating syntax for Kubernetes YAML manifest documents. Helm is the package management tool of choice for Kubernetes.
0 kommentar(er)
