Update the README.md with instructions to usage nano README. deployĬr upload -o devopstales -r helm-charts -p. In your browser go to your github developer settings and create a new personal access token and add full access to the repo.Ĭreate an environment variable for the token: export CH_TOKEN=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sdf The cr index will create the appropriate index.yaml and cr upload will upload the packages to GitHub Releases. Yo can create a chart Helm repository by usin the helm package and helm repo commands but you can simplify your life by using chart-releaser. The werf helm repo commands can be used to interact with Chart Repositories: Use werf helm repo add to add Chart Repository. helm/Chart.yaml should be configured on the system.

After a few minutes you should have a default rendering on your README.md at the provided URL. Use werf helm dependency build to update. Next enable GitHub Pages i the repository settings. gitignoreĬreate brach for GitHub Pages and release: git checkout -orphan gh-pages

git clone helm-chartsĬreate a hem chart in the repository: mkdir charts I chose to hav a README file and an Apache2 licence in mye repository.Ĭlone the repository to start working. Log into GitHub and create a new repository called helm-charts. It also should work.In this post I will show you how you can host your own Helm repository with GitHub Pages. Or if you don't want to make any changes in WSL you could change the DNS server in your network setup (router or host machine). Here is the gist of how to change nameservers in WSL2 (or you could google how to do it). helm install elastic-operator elastic/eck-operator -n elastic-system -create-namespace. Those nameservers return only IPv6 addresses for AAAA queries and IPv4 for A. This is the default mode of installation and is equivalent to installing ECK using the stand-alone YAML manifests. So I came up with a solution to set nameserver to Google or Cloudflare directly in /etc/nf.

helm repo update returns Error: no repositories found. And now I get Error: failed to download 'stable/traefik' (hint: running helm repo update may help). This produces some confusion on OS or Application level (I'm not sure where exactly) and the helm repo index request is stuck in case if the system gets AAAA response before A response. So I adjust the command to be helm install traefik stable/traefik -namespace kube-system -set rbac.enabledtrue. In my case AAAA response contains a lot of A records. This section provides a copy of the older instructions for upgrading Rancher with Helm 2, and it is intended to be used if upgrading to Helm 3 is not feasible. The current instructions for Upgrading Rancher Installed on Kubernetes use Helm 3. You could google what's a difference, but in a short AAAA query is used to get IPv6 addresses. If you are using Helm 2, we recommend migrating to Helm 3 because it is simpler to use and more secure than Helm 2.

When I call helm repo add jetstack I see two DNS queries requests - A and AAAA. As result, I have found that seems like my ISP has a problem with the DNS nameserver. After digging a lot of pages over the internet I have decided to do some Wiresharing of WSL traffic.

Helm update repo