Giter VIP home page Giter VIP logo

Comments (6)

hiddeco avatar hiddeco commented on June 2, 2024

What prevents you from just pinning it to the right version?

Asking because I can see this all go wrong when doing e.g. a disaster recovery, where the dependency has moved on but your values (that are basically married to a version of whatever chart you make use of) still think an older version applies.

from helm-controller.

raffis avatar raffis commented on June 2, 2024

What prevents you from just pinning it to the right version?

Because the version is not necessarily known at that point. Lets say we have a big kustomize base with x helmreleases of internally developed services, if somebody installs that base into a new environment the should get the latest stable releases.

Asking because I can see this all go wrong when doing e.g. a disaster recovery, where the dependency has moved on but your values (that are basically married to a version of whatever chart you make use of) still think an older version applies.

That's actually a good point, another way might be be to let the reconciler write the elected chart version to its own spec if freezeVersion is set. (What the default is doing with * if no version is set).

from helm-controller.

raffis avatar raffis commented on June 2, 2024

That's actually a good point, another way might be be to let the reconciler write the elected chart version to its own spec if freezeVersion is set. (What the default is doing with * if no version is set).

Mhm this would only work if no version was set. Actually I would just need a way to change the default behavior of setting * as spec.chart.version. In my case it should set the elected version.

from helm-controller.

hiddeco avatar hiddeco commented on June 2, 2024

That's actually a good point, another way might be be to let the reconciler write the elected chart version to its own spec if freezeVersion is set. (What the default is doing with * if no version is set).

If it would write it to its own (in-cluster) spec this would not make any difference in case of a disaster recovery? (Assuming Flux2 is used, and the source of truth is in Git).

Actually I would just need a way to change the default behavior of setting * as spec.chart.version. In my case it should set the elected version.

Can't this be done by using an "elected version" Kustomize overlay that is kept in sync together with the values?

from helm-controller.

raffis avatar raffis commented on June 2, 2024

Can't this be done by using an "elected version" Kustomize overlay that is kept in sync together with the values?

Reckon something like this will be the alternative yes.

from helm-controller.

hiddeco avatar hiddeco commented on June 2, 2024

Due to the reason provided in #212 (comment), we are not planning on supporting this.

from helm-controller.

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.