Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image build fails because of Helm having removed the stable repo #49

Open
galexrt opened this issue Dec 22, 2020 · 7 comments
Open

Image build fails because of Helm having removed the stable repo #49

galexrt opened this issue Dec 22, 2020 · 7 comments

Comments

@galexrt
Copy link

galexrt commented Dec 22, 2020

See https://helm.sh/blog/new-location-stable-incubator-charts/ and https://kubernetes-charts.storage.googleapis.com/ returns 403.

A "quick" fix is probably to update Helm to a newer version and / or removing Helm 2.

Log from failed GitHub Actions run:

[...]
Adding stable repo with URL: kubernetes-charts.storage.googleapis.com 
  Error: error initializing: Looks like "kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Failed to fetch kubernetes-charts.storage.googleapis.com/index.yaml : 403 Forbidden
[...]
@JeroenBoesten
Copy link

JeroenBoesten commented Dec 22, 2020

Having the same issue here, did you manage to get the action working again?

@JeroenBoesten
Copy link

For people like me that aren't able to deploy, I manged to find a temporary solution that fixes it quick and dirty by downloading the source and put it in my project repo under '.github/actions/helm-delivery'.
After that I changed the dockerfile to use helm 3.4.2 and removed helm 2 installation.
And use the local action to deploy.

New Dockerfile:


ENV BASE_URL="https://get.helm.sh"

ENV HELM_2_FILE="helm-v2.16.1-linux-amd64.tar.gz"
ENV HELM_3_FILE="helm-v3.4.2-linux-amd64.tar.gz"

RUN apk add --no-cache ca-certificates \
    --repository http://dl-3.alpinelinux.org/alpine/edge/community/ \
    jq curl bash nodejs aws-cli && \
    # Install helm version 3:
    curl -L ${BASE_URL}/${HELM_3_FILE} |tar xvz && \
    mv linux-amd64/helm /usr/bin/helm3 && \
    chmod +x /usr/bin/helm3 && \
    rm -rf linux-amd64

ENV PYTHONPATH "/usr/lib/python3.8/site-packages/"

COPY . /usr/src/
ENTRYPOINT ["node", "/usr/src/index.js"]

Use local action:

# Deploy helm to kubernetes
- name: Deploy to Kubernetes
  uses: './.github/actions/helm-delivery'
  with:

@glend-op
Copy link

glend-op commented Dec 22, 2020

The right fix is to bump version of Helm2 to 2.17.0 https://github.com/deliverybot/helm/blob/master/Dockerfile#L5

Subv added a commit to innovaciongascaribe/helm that referenced this issue Dec 22, 2020
Fixes the problem with helm v2 trying to use the old url for the stable chart repo.

See deliverybot#49 for more details
@Fire7
Copy link

Fire7 commented Dec 28, 2020

@JeroenBoesten
Thank you for your solution, is it work for you?
I'm trying to do same steps, but every time catch some errors, like:

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'is-mergeable-object'

Can you share workaround solution if you have successfully launch it ?

@Fire7
Copy link

Fire7 commented Dec 28, 2020

Another solution:

        # uses: 'deliverybot/helm@v1'  #TODO: Replace after fix https://github.com/deliverybot/helm/issues/49
        uses: elseu/[email protected]

Works for me

oestrich added a commit to oestrich/ex_venture that referenced this issue Jan 3, 2021
apt-get-brisket added a commit to JambbTeam/deliverybot-helm that referenced this issue Jan 4, 2021
@colinjfw
Copy link
Collaborator

colinjfw commented Jan 9, 2021

Merged #50 please let me know if that resolves the issue.

@JeroenBoesten
Copy link

Merged #50 please let me know if that resolves the issue.

Can confirm that this resolves the issue, thank you.

apt-get-brisket added a commit to JambbTeam/deliverybot-helm that referenced this issue May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants