Wha's the repo url?

[StathisKap]

Type of question

Implementation Assistance

Support question

I've run the commands i the Get Started and they don't work. What is the URL for the helm repo?

NiFiKop version

No response

Golang version

No response

Kubernetes version

No response

NiFi version

No response

[mh013370]

The helm charts are hosted as OCI images here:

• https://github.com/orgs/konpyutaika/packages/container/package/helm-charts%2Fnifikop
• https://github.com/orgs/konpyutaika/packages/container/package/helm-charts%2Fnifi-cluster

To install,

helm upgrade --install nifikop oci://ghcr.io/konpyutaika/helm-charts/nifikop:1.5.0 -n nifi --set namespaces={"nifi"}

[StathisKap]

Hello @mh013370. Thank you for the quick reply. I keep getting these though

$ kopeo list-tags docker://ghcr.io/konpyutaika/helm-charts/nifikop                                                                                                                                                                            

{
    "Repository": "ghcr.io/konpyutaika/helm-charts/nifikop",
    "Tags": [
        "0.8.0",
        "0.9.0",
        "0.10.0",
        "0.11.0",
        "0.0.1",
        "0.12.0",
        "0.13.0",
        "0.13.1",
        "0.14.0",
        "0.14.1",
        "0.15.0",
        "0.0.2",
        "0.16.0",
        "1.0.0",
        "1.1.0",
        "1.1.1",
        "1.2.0",
        "1.3.0",
        "1.3.1",
        "1.4.0",
        "1.4.1",
        "1.5.0"
    ]
}
$ helm upgrade --install nifikop oci://ghcr.io/konpyutaika/helm-charts/nifikop:1.5.0 -n nifi --set namespaces={"nifi"}
Release "nifikop" does not exist. Installing it now.
Error: invalid_reference: invalid tag

$ helm upgrade --install nifikop oci://ghcr.io/konpyutaika/helm-charts/nifikop --version 1.5.0 -n nifi --set namespaces={"nifi"} 

Release "nifikop" does not exist. Installing it now.
Error: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Akonpyutaika%2Fhelm-charts%2Fnifikop%3Apull&scope=repository%3Auser%2Fimage%3Apull&service=ghcr.io: 403 Forbidden

does nifikop work on k3s on Hetzner machines? Or is it mostly meant for GKE and Azure?

[mh013370]

nifikop is vendor agnostic - it doesn't matter what the kubernetes runtime is. It works on k3s, k3d, rke2, eks, openshift, etc.

You need to authenticate with Github with helm registry login using an access token. Then your helm client will be happy.

[StathisKap]

That's great to hear!

I apologise but I must be doing something wrong. I've logged in to GitHub with helm, and I'm still getting the same errors. Below you can see me running the helm registry login command a second time.

└─(14:33:54 on main ✹ ✭)──> helm registry login https://github.com
Username: StathisKap
Password:
Error: error storing credentials - err: exit status 1, out: `The specified item already exists in the keychain.`

└─(14:34:14 on main ✹ ✭)──> helm upgrade --install nifikop oci://ghcr.io/konpyutaika/helm-charts/nifikop:1.5.0 -n nifi --set namespaces={"nifi"}
Release "nifikop" does not exist. Installing it now.
Error: invalid_reference: invalid tag

└─(14:34:39 on main ✹ ✭)──> helm upgrade --install nifikop oci://ghcr.io/konpyutaika/helm-charts/nifikop --version 1.5.0 -n nifi --set namespaces={"nifi"}
Release "nifikop" does not exist. Installing it now.
Error: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Akonpyutaika%2Fhelm-charts%2Fnifikop%3Apull&scope=repository%3Auser%2Fimage%3Apull&service=ghcr.io: 403 Forbidden

Don't know if it's relevant but I'm on MacOS

[mh013370]

You need to helm registry login ghcr.io. As with docker, helm logins are all repository (hostname) based:

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry#authenticating-with-a-personal-access-token-classic

[StathisKap]

It's deployed!!!. Thank you so much for your help and patience. I really appreciate it Mr Michael

[mh013370]

Nice. Let us know if you have any more questions though slack might be slightly more responsive