Error: INSTALLATION FAILED: failed to download "ory/hydra"

[hongbo-miao]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] This issue affects my Ory Cloud project.
• [X] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe the bug

I am trying to install Ory Hydra on a local Kubernetes created by k3d using Helm based on https://www.ory.sh/docs/hydra/guides/kubernetes-helm-chart

However, I failed at the first step installing. Any idea? Thanks! 😃

Reproducing the bug

I tried to run

helm install --generate-name \
    --set 'hydra.config.secrets.system=$(LC_ALL=C tr -dc 'A-Za-z0-9' < /dev/urandom | base64 | head -c 32)' \
    --set 'hydra.config.dsn=memory' \
    --set 'hydra.config.urls.self.issuer=https://my-hydra/' \
    --set 'hydra.config.urls.login=https://my-idp/login' \
    --set 'hydra.config.urls.consent=https://my-idp/consent' \
    ory/hydra

Relevant log output

However, I got error

Error: INSTALLATION FAILED: failed to download "ory/hydra"

Relevant configuration

No response

Version

N/A

On which operating system are you observing this issue?

macOS

In which environment are you deploying?

Kubernetes with Helm

Additional Context

> kubectl version --short

Client Version: v1.23.4
Server Version: v1.22.6+k3s1

> helm version --short

v3.8.1+g5cb9af4

[hongbo-miao]

I succeed after running this first

helm repo add ory https://k8s.ory.sh/helm/charts

Then I can install. I think might worth adding to the document. 🙂

[Demonsthere]

Hi there. This piece of documentation is actually in the root of the documents: http://k8s.ory.sh/helm/ 😉

[hongbo-miao]

Oh yeah, originally I didn't find that. I was following this tutorial https://www.ory.sh/docs/hydra/guides/kubernetes-helm-chart Worth adding there too! 😊

[github-actions[bot]]

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

• open a PR referencing and resolving the issue;
• leave a comment on it and discuss ideas on how you could contribute towards resolving it;
• leave a comment and describe in detail why this issue is critical for your use case;
• open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️