Missing Charts #31039
Comments
Rumbles
added
the
tech-issues
|
Just wanted to chime in that I'm seeing the same behavior. I found this issue after receiving the same issue attempting to check renovatebot PRs for both the I've noticed the tags do appear to be available in docker.io when looking at the tags for docker images in a given chart. I only use the chart default versions so this is surprising we'd see this error. I'm wondering if this might have something to do with needing to authenticate with a Docker account (purely a guess in this case). I'm going to look into how to achieve that. |
|
I took the following steps (spoiler -- still not successful)
resource "kubernetes_secret" "docker_io_access_token" {
metadata {
name = "docker-io-access-token"
# NOTE: this is my namespace, yours will of course differ
namespace = kubernetes_namespace.products.metadata[0].name
}
type = "kubernetes.io/dockerconfigjson"
data = {
".dockerconfigjson" = jsonencode({
auths = {
"ghcr.io" = {
"username" = "MY_USERNAME"
"password" = "MY_ACCESS_TOKEN" # Docker Personal Access token scoped to read packages only
"email" = "MY_EMAIL"
"auth" = base64encode("MY_USERNAME:MY_ACCESS_TOKEN")
}
}
})
}
}
set_list {
name = "image.pullSecrets"
value = [kubernetes_secret.docker_io_access_token.metadata[0].name]
}
So (I think?) at this point I've ruled out it having anything to do with docker creds. |
|
Found this, which seems relevant: helm/helm#13466 The Bitnami charts are listed here I think: https://repo.broadcom.com/bitnami-files/index.yaml The issue seems to be that the OCI chart definition includes the version -- here's
|
|
From what I can tell, this part of #30402 might be the cause (and subsequent modifications). Looks like the index has the OCI reference including a tag, and then also includes the version, which helm then parses into a duplicate tag because it uses URL + version: I'll see if I can maybe submit a pull request, assuming I'm not somehow way off. |
|
Nevermind -- I see here that the issue is that Bitnami appears to be defaulting to OCI formats: #30519 (comment) In the https format of the URL, the Bitnami index includes the tag for the version, which then has the version additionally appended to it by Helm, causing in invalid tag error. I updated my repos in helm to use the OCI format (e.g. from Sorry for all the comments while I flailed about. 😅 |
|
Hi @SeanKilleen thanks for the info, I was not aware of this change. The strange part for me was that it worked one day, then stopped working the next |
|
As you rightly said and as reported in helm/helm#13466, this problem stems from how the Why is this issue appearing now?Historically, Bitnami Helm charts were accessed by adding the Bitnami repository to the Helm CLI: or by directly installing/pulling a specific Helm chart using the In April 2023, Bitnami introduced support for the OCI format, recommending OCI-based installation as the primary method going forward. For example: As detailed in our recent announcement and #30110, the traditional method is now being deprecated. Consequently, the index.yaml served at |
Name and Version
bitnami/keycloak 24.3.0
What architecture are you using?
None
What steps will reproduce the bug?
Yesterday I set up a new keycloak server using 24.3.0, and I this morning I deleted everything to start again, but I suddenly get:
Error: invalid_reference: invalid tagI tried manually to confirm and I get the same error locally, and the last 3 chart versions are also not available when I check, only 24.2.0 was available.
Is this to be expected? I thought tags should not be removed like this? Was there some rollback and some versions lost?
Sorry if this is the wrong place to report, but I was a bit confused
Are you using any custom parameters or values?
No response
What is the expected behavior?
Charts should be available
What do you see instead?
however 24.2.0 is the first version I can pull, 24.2.1, 24.2.2, 24.2.3 and 24.3.0 are all
invalid tagAdditional information
No response
The text was updated successfully, but these errors were encountered: