Giter VIP home page Giter VIP logo

Comments (2)

allenporter avatar allenporter commented on June 30, 2024

Hi, definitely open to being flexible here. The main reason this is disabled is so that helm only looks at things defined in the repository. I am not super familiar with the details of OCI other than basics to make it work, nor how to configure private repos. Happy to talk through a solution (one of the options you propose may be the right one) though may need some help understanding a little more what the workflow is supposed to look like. Can you give me a little more background on how you set this up and specify private oci helm chart repos in practice?

There is also discussion in #301 so wondering if a single approach solves both.

from flux-local.

eloo-abi avatar eloo-abi commented on June 30, 2024

@allenporter okay that sounds good so far :)

For the OCI helm chart we have Harbor setup up (https://github.com/goharbor/harbor), which we also use for our docker images already.
The main idea is to reuse the OCI format to store and exchange helm chart instead of tar.gz
More detail can be found in the helm docs: https://helm.sh/docs/topics/registries/

And the issue with the hardcoded flag is that adding credentials will not work because its not used afterwards.
Normally we do

helm registry login ...

this will be written into the ~/.config/helm/registry/config.json and then reused to authenticate when calling OCI registries. (its the same format as docker/config.json

The path what file should be used to lookup registry auths can be configured with this parameter

      --registry-config string          path to the registry config file (default "~/.config/helm/registry/config.json")

And there is the problem because this is hardcoded to /dev/null right now ans so its not possible to use private OCI.

I guess the best solution without a breaking change would be to expose this parameter to the flux-local cli and keep /dev/null as default.
So i could be set if necessary but if not needed nothing is going to be changed.

As #301 is referring to "http" charts i'm not sure if this would fix it here as well. But i would expect that helm repo add ... --username --password should work already.

If not exposing

      --repository-config string        path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

could be the fix here as well.

Best regards

from flux-local.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.