-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Helm chart is not automatically released on microk8s
#2262
Comments
Given nothing related to git is logged after Did you add the public key to your repository? |
@hiddeco I added my public key in github. After i added i ran
|
@hiddeco any idea about this ? |
Made a fresh fork of After closly following all steps on https://github.com/fluxcd/flux/blob/master/site/helm-get-started.md, and adding the public key as a read/write deploy key to the repository.
Given the above I can think of two things:
|
@hiddeco I tried the same with minikube. Works fine . But what is the reason it behaves differently in microK8s. confused !!! |
Given
and
I think you may have had a (temporary) network related hick-up. Can you try the whole setup again on |
I tried many times , microk8s is failing always with fluxcd :( |
microk8s
I had no problem using flux with MicroK8s. Here is roughly what I did.
Create the sa as described in the startup doc. Install helm
Add the key to github repo.
Wait a few seconds and you get this picture:
I do not look why the demo is failing for me. With:
|
@ktsakalozos the “Too Many Requests (HAP429)“ error is due to Flux hitting the Docker Hub rate limiter, but kubelet should retry the image pull after a couple of minutes. We run the same setup in CircleCI as part of the end-to-end testing. I haven’t seen the rate limit error there but maybe from your IP there was a lot of traffic towards Docker Hub. |
There are still rate limiting issues and we have seen failure to pull all image metadata for automated workloads resulting in a halt to applies. This is one of the major limitations in Flux v1 and cannot be fixed, without breaking changes as explained through https://fluxcd.io/docs/guides/sortable-image-tags/ This is fixed in Flux v2. Closing, thanks for using Flux! |
Describe the bug
I am trying to deploy helm chart as per this document https://github.com/fluxcd/flux/blob/master/site/helm-get-started.md
Expected behavior
I ran the following command as per the document
Logs
flux-helm-operator logs
flux logs
Additional context
Add any other context about the problem here, e.g
Note: i am running under microk8s
The text was updated successfully, but these errors were encountered: