REQUEST: New membership for @gecube

[gecube]

GitHub username

@gecube

Requirements

• I have reviewed the community membership guidelines in community-roles.md
• I have subscribed to the cncf-flux-dev e-mail list https://lists.cncf.io/g/cncf-flux-dev/join
• I am actively contributing to 1 or more fluxcd GitHub org repos (e.g. Flux, Flagger)
• I have enabled 2FA in GitHub
• I have two sponsors who meet the sponsor requirements listed in the community membership guidelines
• I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors

• @kingdonb
• @matheuscscp

List of contributions to the Flux project

PRs authored:

• chartutil: add Literal mode to ValuesReference (helm --set-literal semantics) pkg#1218 — chartutil: add Literal mode to ValuesReference (helm --set-literal semantics for HelmRelease valuesFrom); shipped with helm-controller in Flux v2.9.2
• docs: document literal field on valuesFrom helm-controller#1503 — documentation for the new literal field on valuesFrom
• fix: keep failed-to-prune resources in status.Inventory (#1664) kustomize-controller#1665 — fix: keep failed-to-prune resources in status.Inventory so pruning is retried on the next reconciliation
• kustomize: preserve existing image fields when merging spec.images pkg#1266 (open) — kustomize: preserve existing image fields when merging spec.images, fixes Flux Kustomization's spec.images with newName strips existing image tags flux2#5787; includes reproduction repo https://github.com/gecube/flux2-5787-repro
• Fix Gitlab -> GitLab in README.md terraform-provider-flux#770 — docs fix
• Add Aenix's cozystack to the flux ecosystem website#1993, Add Ænix to adopters website#1990, Add Zodia Markets to adopters website#1989 — ecosystem and adopters entries
• Fix installation on talos.dev flux2-monitoring-example#25 — fix installation on Talos
• Fix the indentation issues in example image-reflector-controller#286, Fix typo in API spec docs kustomize-controller#523 — docs fixes

Issues filed, triage and verification work:

• Resources not pruned after a rapid series of commits where intermediate kustomize build output is broken kustomize-controller#1664 — reported the prune-loss bug after rapid commits with broken intermediate builds, then fixed it myself in #1665
• Flux Kustomization's spec.images with newName strips existing image tags flux2#5787 — root-cause analysis of spec.images newName stripping existing tags, reproduction repo, fix PR kustomize: preserve existing image fields when merging spec.images pkg#1266
• flux push artifact to registry w/ self-signed certificate fails though --insecure-registry is given flux2#5986 — verified the --insecure-registry TLS regression is fixed in v2.9.2 with an A/B test setup
• Image update automation removes --- at top of the file flux2#5644 — A/B reproduction of image automation dropping the leading --- document separator; traced upstream to feat: preserve initial document separator with kyaml kubernetes-sigs/kustomize#6062
• flux seems to struggle with UTF-16 LE encoded files written from Windows PowerShell flux2#1126 — root-caused a stale UTF-16 manifest report to apimachinery's LineReader, posted analysis so it can be closed
• Earlier reports and discussions: Flux HelmRelease not deploying CRDs in template dir flux2#5805, make strategy inside UpdateStrategy optional flux2#5457, make strategy inside UpdateStrategy optional image-automation-controller#941, Incorrect error message regarding cli flux2#5261, Change the default behaviour for components-extra from opt-in to opt-out scenario flux2#4443, bootstrap: More details for flux-system context deadline exceeded  flux2#4411, notification controller does not strip new line and the end of URL notification-controller#760, add namespace filter '*' notification-controller#640, Cryptic error message when git is not available source-controller#1239, Cryptic message when GPG binary is not present. kustomize-controller#966, Cryptic error message when there is no write access to SSH key image-automation-controller#491
• Flux v1 era: flux leaks https password in git error messages flux#2655, Provide ability to trigger CI once flux applies changes flux#2710, More verbose message on "invalid image ID" flux#1290

Background: Flux user in production since 2019 (Flux v1), currently operating Flux v2 across a multi-cluster EKS fleet.

Flux subprojects I am involved with: flux2, pkg, helm-controller, kustomize-controller, image-automation-controller, source-controller, notification-controller, website, terraform-provider-flux

Code of Conduct

• I agree to follow this project's Code of Conduct

[kingdonb]

Yeah this guy is great! 👍

[gecube]

@kingdonb thanks for the respectful words.

[matheuscscp]

Agreed, George has been active in the community for a good while 🤗

[matheuscscp]

Hey @gecube, I understand you'd like to become a member and I appreciate your contributions over the years, which are significant and deserve the reward.

But please stop spamming AI slop in the Flux repos, I'm getting flooded by notifications from you with walls of text generated by AI, which is clearly against Flux's guidelines:

https://github.com/fluxcd/flux2/blob/main/CONTRIBUTING.md#ai-coding-assistants-guidance

Trim down the verbiage in the PR description, commit messages and code comments. When engaging with Flux maintainers please refrain from using AI Agents to generate responses, we want to talk to you, not to your AI Agent.

By spamming that much AI slop you are currently risking getting banned from the org instead of becoming a member.

[stefanprodan]

+1 from me

PS. @gecube thanks for going over old issues, but please do it in batches, 10 per week max. My brain can not take more 😄

[matheuscscp]

+1 from me

PS. @gecube thanks for going over old issues, but please do it in batches, 10 per week max. My brain can not take more 😄

Agreed! It was indeed very productive, but needs to come at the human pace!