GithubHelp home page GithubHelp logo

Comments (1)

tkrullmann avatar tkrullmann commented on June 18, 2024

Hi,
I'm not 100% sure what you are trying to do, maybe explain your goal so I can help better.

My guess is that you are trying to construct a custom chart around stable/airflow with a user-specific values.yaml, and then install that. In that case Many charts from the public repositories allow heavy customization, so I'd try to avoid creating a chart at all, and just use the chart from the repo and use the releases feature to pass the user-defined values.

helm {
    // configure namespace and downloadClient like in your script

    repositories {
        google { // or give it any name you like
            url 'https://kubernetes-charts.storage.googleapis.com/'
        }
    }

    releases {
        from 'google/airflow'
        version = '6.10.4'

        // put your customization values for the release here
        values = [key: 'value']
        valueFiles.from 'my-values.yaml'
    }
}

Some additional pointers that might help:

  • Anything that you put in the charts.myChart block will only contribute to the chart (i.e. not beyond the helm package step). The values.yaml from the chart are just the defaults that will be packaged with the chart.
  • You are probably not using filtering the way it's intended. It's a build-time replacement of values in the chart, intended for things like version and project name that you don't want to repeat in the chart. It shouldn't be used for environment or user-specific values. Also, filtering is a feature specific to this plugin, Helm itself doesn't know about it and it won't be involved after the chart is packaged.
  • Values YAML files that should be passed to helm install for configuring a release should be added to the release, not the chart.
  • If your release name is dynamic, I would recommend using a fixed name in the DSL anyway, and set the releaseName property on the release. The DSL name is what you use to refer to it in the Gradle script, and what is used for constructing task names. The release name is what is passed to helm install. (It just happens to default to the DSL name for convenience.)
  • You can always check the actual Helm CLI invocation arguments by running Gradle with --info.

from gradle-helm-plugin.

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.