Improve kubernetes documentation. #138
Conversation
Main change is the addition of a note to clarify how to authenticate with Helm. Not really an issue, but I ran into this because my token was expired and had to go through docs again.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| :::note | ||
|
|
||
| You must first be authenticated to ghcr.io following | ||
| [these instructions](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic). | ||
|
|
||
| ::: | ||
|
|
There was a problem hiding this comment.
I just double-checked, this is not necessary - our images are public. I think it only bit you because you had previously logged in with a now-expired token?
There was a problem hiding this comment.
I had to log into GHCR anyway, it was not working without this step. It might be an issue with my setup.
There was a problem hiding this comment.
It must be, because I tried from a VM that has never logged into ghcr.io, also on my main laptop I did a docker logout ghcr.io just to be sure, and have not had an issue.
When did you see it, when trying to run helm to apply the chart? Any other image pulls would be happening from inside the cluster and not from your local Docker client.
Perhaps instead we make this a troubleshooting item at the bottom, in case people run into the scenario you did?
|
I addressed these in my last push while also updating for the new multi-namespace support. Thanks! |
Main change is the addition of a note to clarify how to authenticate with Helm. Not really an issue, but I ran into this because my token was expired and had to go through docs again.