|
Re: Self nomination to help maintain helm/helm
+1 for Scott! thanks for all the work you do! Em qui., 16 de set. de 2021 às 21:08, Scott Rigby <scott@...> escreveu:
|
|
|
|
Self nomination to help maintain helm/helm
Hi again everyone 👋
Since last week's Helm dev call, I planned to self nominate to help with helm/helm triage via the new Triage role. I've also already been wanting to volunteer time to help with helm/helm repo maintainer duties for a while now.
If I understand the Triage Maintainer HIP and Governance correctly, I would only need to self nominate as a core maintainer to be able to help with both of these. I'm I need to self nominate for the triage maintainer role too, please lmk 🙂 I've been on the Helm team since 2017. I'm a Helm Org maintainer, and Charts maintainer (the team who oversaw the now archived helm/charts, as who continues to maintain charts automation and tooling such as helm/chart-testing, helm/chart-releaser, and the Helm Charts GitHub actions in this working demo). However while I have contributed a bit to Helm core in the past, it's been a while and I have never been a maintainer of the helm/helm repo. I'm currently on the DX team at Weaveworks, and help maintain other CNCF community projects such as Flux, and OpenGitOps, and co-chair the GitOps Working Group under App Delivery TAG. In addition to other helm/helm duties, I'd like to help us keep prioritizing the Helm SDK as the Helm project continues to evolve. I've been spending time with k8s controller-runtime as a step toward helping more with the Flux Helm Controller, which is an example of a project that makes full use of the Helm's SDK. So I will already be a more active SDK end user, as well as be more active helping support others who use Helm's SDK. I'm finally in a role that can support me doing some of this, and happy to help with helm/helm maintenance however I can if current maintainers think it makes sense. Tweets: https://twitter.com/r6by
xo, Scott -- Scott Rigby
Developer Experience, Weaveworks |
|
|
|
Triage Maintainer Self Nomination: Allen Bai
Allen Bai
Hello everyone!
As discussed during today's (Sept. 9) weekly Helm developer meeting, I'd like to nominate myself as one of the triage maintainers. I'm a software engineer at Red Hat and working on Helm integration within OpenShift. I've been attending weekly Helm developer calls for ~3 months since I joined the Helm team at Red Hat on May 25th. Although relatively new to `helm/helm` and Go, I am actively learning and catching up. I would like this opportunity to work with other Helm maintainers to triage and review code and contribute to the Helm community. Doc references: - Triage Maintainer HIP: https://github.com/helm/community/blob/main/hips/hip-0014.md - Governance Documentation: https://github.com/helm/community/blob/main/governance/governance.md Github: https://github.com/zonggen Best regards, Allen Bai |
|
|
|
[HIP] cascade option for uninstall and upgrade commands
Péter Laukó <peter.lauko@...>
Hi, I would like to propose a 'cascade' option for the uninstall and upgrade commands. The current implementation of these commands hardcodes metav1.DeletePropagationBackground and removes all dependent objects unconditionally. This is the preferred behaviour for most of the time, but I think it would make sense to make it configurable. For example we set owner references between custom resources (default configuration pieces provided by our application and their user overrides) and most of the time we would like them to come and go together. However if an upgrade fails, the owned objects (user overrides) should be kept in place, and being able to turn off cascading would make fixing the failed release easier. Please let me know if you think this idea makes sense and I'm happy to prepare a formal proposal and provide the patch. Best, Peter |
|
|
|
[proposal] Reference packaged value files
Riccardo Piccoli
Hi all!
I am planning to write an HIP about referencing packaged values in dependency charts. Before doing that, I would like to check if there is any interest in the proposal, or if I should just implement it as a plugin. ## Problem Some of our applications are composed by multiple independent software, bound together by a router. As a practical example, we can have the following FooBar application: - Router (routes incoming requests) - Foo Server (serving /foo/* pages) - Bar Server (serving /bar/* pages) * Foobar application needs to be deployed in different environments (i.e. dev/staging/prod) and different regions (i.e. europe/us/asia) * Foo and Bar are developed independently, so we should change its dev/staging/prod/region values in the same repo. * Some of the application (Router-Foo, Router-Bar in this case) are be related, so we want to define them in the same place ## Current solutions Unfortunately I can't see a clean way to do this at the moment, as we cannot reference packaged value files. We could: 1) organize all possible dimensions (cluster, environment, etc) in keys with enable/disable switch, and enable/disable from parent chart. 2) write all values in parent chart Solution one is very hacky, and would greatly complicate our charts. Solution two will complicate development of each solution, as values should be modified in multiple parts of the code (in our case, in multiple repos) ## Proposed solution Ideally it would look something like this: Parent chart: foobar ├── Chart.yaml ├── values.yaml ├── values.dev.yaml └── values.staging.yaml The dependency section would look something like: dependencies: - name: router version: 1.0.0 repository: "@mycharts" - name: foo version: 1.0.0 repository: "@mycharts" - name: bar version: 1.0.0 repository: "@mycharts" subcharts: foo ├── Chart.yaml ├── values.yaml ├── values.dev.yaml ├── values.europe.yaml ├── values.us.yaml ├── values.asia.yaml └── values.staging.yaml bar ├── Chart.yaml ├── values.yaml ├── values.dev.yaml ├── values.europe.yaml ├── values.us.yaml ├── values.asia.yaml └── values.staging.yaml ## Proposed implementation We could reference dependencies' *packaged value files* as follows: `helm upgrade . -f values.yaml -f foo/values.europe.yaml -f foo/values.yaml -f bar/values.europe.yaml -f bar/values.yaml` For example, if this is run from `foobar` directory, helm could check: - if value file exists in the filesystem, it will be used - if not, we check if the prefix (until `/` char) is a dependency (name/alias). If it is, we chan look for the file there This would be preferable to a custom switch, so it can be integrated with already existing tools (i.e. ArgoCD, skaffold, etc) without the need of a downstream change. Any feedback you might have is welcome! Cheers, Riccardo |
|
|
|
Use a config from a sub-chart to an other
Stéphane Brunner
Hello, I write this in the dependencies or my Chart.yaml - name: redis-config repository: file://../../configs/redis import-values: - child: config parent: redis - name: redis version: 14.8.6 And I expected that all the config is injected in the Redis chart but only the empty dict will be filled ... Is it possible to have a chart with a config and use it in another chart? My goal is to share some configuration without impose the version of the chart. CU Stéphane --
|
|
|
|
Custom resource ordering in Helm
Gabe Alford <redhatrises@...>
Hello, I wanted to ask what the status is on the ordering of custom resources in Helm. I need to deploy PSP, SCC, and a MutatingWebhookConfiguration in a certain order. I see a couple of PRs that address this like https://github.com/helm/helm/pull/9534 and https://github.com/helm/helm/pull/8448. Obviously, the solution to handling resource ordering is implemented in different ways. Is there movement on one solution vs the other? Or are they dead in the water? Or....? And maybe the capability is already there, and I am just missing it. Any help would be appreciated! Thanks, Gabe |
|
|
|
Re: [EXTERNAL] [cncf-helm] Application for joining Helm organization
苑雄雄
Yes, I want to be a maintainer for helm project. it is is my pleasure. I will spend more time maintaining the community and solving problems. At the beginning, you can give me viewer permission first. At 2021-06-26 03:26:02, "Matt Butcher" <Matt.Butcher@...> wrote:
|
|
|
|
Re: [EXTERNAL] [cncf-helm] Application for joining Helm organization
苑雄雄
Yes, I want to be a maintainer for helm project. it is is my pleasure. I will spend more time maintaining the community and solving problems. At the beginning, you can give me viewer permission first. At 2021-06-26 03:26:02, "Matt Butcher via lists.cncf.io" <matt.butcher=microsoft.com@...> wrote:
|
|
|
|
Re: [EXTERNAL] [cncf-helm] Application for joining Helm organization
Matt Butcher <matt.butcher@...>
Which project are you interested in joining? I know you are active on github.com/helm/helm. Do you want to be a maintainer for that project?
From: cncf-helm@... <cncf-helm@...> on behalf of 苑雄雄 via lists.cncf.io <aiopsclub=163.com@...>
Sent: Thursday, June 24, 2021 6:20 PM To: cncf-helm-core-maintainers@... <cncf-helm-core-maintainers@...>; cncf-helm@... <cncf-helm@...> Subject: [EXTERNAL] [cncf-helm] Application for joining Helm organization Hello, I'm yxxhero.
I take the liberty to send you an email, After a long time using helm and reading the source code of helm, I'm more and more familiar with helm. Now I'd like to join the helm
organization and make more contributions. I'm looking forward to your reply. Thanks very much.
I have already read up on the
Helm Maintainer's Onboarding Guide, helm's
governance as well as the
team structure.
Because I am in china. so I can't attend the
weekly Helm developer call. email is ok for me. I will actively participate in the activities related to helm.
github:
https://github.com/yxxhero, Currently, I am improving this PR: https://github.com/helm/helm/pull/9482, I
hope everyone can give me some help, and I will participate more actively in the community.
|
|
|
|
Application for joining Helm organization
苑雄雄
Hello, I'm yxxhero. I take the liberty to send you an email, After a long time using helm and reading the source code of helm, I'm more and more familiar with helm. Now I'd like to join the helm organization and make more contributions. I'm looking forward to your reply. Thanks very much. I have already read up on the Helm Maintainer's Onboarding Guide, helm's governance as well as the team structure. Because I am in china. so I can't attend the weekly Helm developer call. email is ok for me. I will actively participate in the activities related to helm. github: https://github.com/yxxhero, Currently, I am improving this PR: https://github.com/helm/helm/pull/9482, I hope everyone can give me some help, and I will participate more actively in the community.
|
|
|
|
Re: Where to see previous discussions for this mailing list
Matt Fisher <matt.fisher@...>
Should be available at https://lists.cncf.io/g/cncf-helm/topics. Are you able to see that list?
Matt
From: cncf-helm@... <cncf-helm@...>
On Behalf Of Robert Campbell via lists.cncf.io
Sent: June 23, 2021 7:06 PM To: cncf-helm@... Subject: [cncf-helm] Where to see previous discussions for this mailing list
Since this is the recommended starting point for vetting proposals. Where would one see the previous discussions/vetting of ideas that this mailing list has conducted?
Thanks, |
|
|
|
Where to see previous discussions for this mailing list
Robert Campbell <realy2@...>
Since this is the recommended starting point for vetting proposals. Where would one see the previous discussions/vetting of ideas that this mailing list has conducted? If there is not a historic record of the discussions/vetting, is this the right medium for this discussion/vetting? Thanks, Robert Campbell This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. |
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
+1 Maith thú Martin! |
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
Adam Reese
For that rockstar... +1
From: cncf-helm@... <cncf-helm@...> on behalf of Matt Butcher via lists.cncf.io <matt.butcher=microsoft.com@...>
Sent: Tuesday, May 25, 2021 9:51 AM To: cncf-helm@... <cncf-helm@...> Cc: MARTIN HICKEY <martin.hickey@...> Subject: [cncf-helm] Org Maintainer Nomination: Martin Hickey
I would like to nominate Martin Hickey as a Helm org maintainer, as described in the Helm Org Governance document: https://github.com/helm/community/blob/main/governance/governance.md
Martin is a long-standing community member, a maintainer on multiple Helm projects, and an excellent ambassador of the Helm community.
Per the governance documents, this begins the three-week nomination process, which will end on June 15, 2021. At that time, a private Condorcet-style vote will be taken, in which all maintainers for all Helm projects are eligible to vote once. Martin must obtain
a 2/3 majority of those that voted.
Happy Helming,
Matt Butcher
Chair, Helm Organization
|
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
+1 for Martin! 🌟 On Thu, Jun 17, 2021 at 11:50 AM Josh Dolitsky <jdolitsky@...> wrote:
--
Bridget |
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
Josh Dolitsky
+1 ! On Thu, Jun 17, 2021 at 12:50 PM Scott Rigby <scott@...> wrote:
|
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
+1 💯🎉 On Thu, May 27, 2021 at 9:02 AM Marc Khouzam <marc.khouzam@...> wrote:
|
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
Absolutely! +1 On Tue, May 25, 2021 at 5:15 PM Adnan Abdulhussein <prydonius@...> wrote:
|
|
|
|
Re: Org Maintainer Nomination: Martin Hickey
Adnan Abdulhussein
Huge +1 :)
Adnan
On May 25, 2021, 13:56 -0700, Reinhard Nägele <unguiculus@...>, wrote: +1 |
|
|