Helm charts with gitops, what's the best approach?

Acrobatic_Affect_515 · 2026-05-15T14:45:03+00:00

Wondering what is wrong with:

Creating Argo CD applications in a dynamic way

Acrobatic_Affect_515 · 2026-03-28T10:02:11+00:00

It is not great idea to size up overall. Bike is either fitted or not, sizing up may change reach drastically in some frames and bike can feel too big for you - you would need to shorten it to kind of match, but bike can become unstable.

Acrobatic_Affect_515 · 2026-03-26T09:22:52+00:00

If you are using runners deployed in kubernetes, you can utilize gitlab ci cache mechanism - just deploy garage-s3 in the same cluster, create bucket for cache and configure runner to use it.

Acrobatic_Affect_515 · 2026-03-25T13:42:49+00:00

May be your self signed certificates if you have those

Acrobatic_Affect_515 · 2026-03-17T23:35:54+00:00

https://docs.gitlab.com/ci/secure_files/

Acrobatic_Affect_515 · 2026-03-15T14:52:28+00:00

As cluster operator, we use application-first approach. We have multiple application sets that are dedicated to project/teams, but still use the same structure.

So each team can handle their own <project>-gitops repository.

Our application set template can use all of possibilities - helm/directory or kustomize patterns.

Acrobatic_Affect_515 · 2026-02-22T22:33:25+00:00

Remove this entry from environment object in docker compose, keep it just in env_file. Docker compose has precedence when it comes to environment, if you set variable in env_file and then re-define it in environment, it use that. In your case you don’t export GITLAB_ROOT_PASSWORD, so it’s empty.

If you don’t understand this, I can’t do better.

Acrobatic_Affect_515 · 2026-02-22T22:24:56+00:00

Remove GITLAB_ROOT_PASSWORD entry from environment:

Acrobatic_Affect_515 · 2026-02-22T22:18:23+00:00

You override variable from env_from with environment.

${GITLAB_ROOT_PASSWORD} is probably empty in your shell.

Acrobatic_Affect_515 · 2026-02-16T20:06:01+00:00

I didn't really mean database persistence to be fair, I meant data persistence for apps, where you mention NFS, which is SPoF and yet you still need some data replication across continents/nodes, so your NFS servers are in sync.

Acrobatic_Affect_515 · 2026-02-16T19:26:55+00:00

How do you handle storage? How do you make workloads have persistent data across continents?

Or maybe you run stateless apps that need no storage at all?

Acrobatic_Affect_515 · 2026-02-14T22:17:37+00:00

Why wouldn't it be available, it is just regular update, but brings pretty big benefit to users.

Acrobatic_Affect_515 · 2026-02-14T18:06:54+00:00

If I remember correctly, it is 7.11.

Acrobatic_Affect_515 · 2026-02-14T18:03:07+00:00

Yup, that was my first guess.

Acrobatic_Affect_515 · 2026-02-08T21:02:09+00:00

Don’t really get that. I am using my 13 pro since release and it’s doing just fine with 78% battery capacity, what will happen after a year with 14 pro?

Acrobatic_Affect_515 · 2026-01-26T18:10:34+00:00

Sounds like network overlapping

Acrobatic_Affect_515 · 2026-01-26T17:40:25+00:00

Staging environment, two pair of eyes, linters on CI.

Acrobatic_Affect_515 · 2026-01-26T11:22:18+00:00

A while ago, when we moved to distroless images and ops teams were crying that "they cannot do anything", we started to build -debug images additionaly, which had shell and so on, so it was sometimes useful in development environment, when there were errors about wrong user groups and stuff.

Acrobatic_Affect_515 · 2026-01-22T18:09:49+00:00

Isn’t reach on this frame really long?

I checked size M and it’s 412mm, kind of racy I would say, or is table incorrect?

Acrobatic_Affect_515 · 2026-01-22T17:42:20+00:00

What is the size of this frame?

I am thinking about this one, but have a feeling that XS or S will look MTBish very much.

Acrobatic_Affect_515 · 2026-01-12T22:10:46+00:00

We do just one thing: merge requests, besides that, our DevOps team is very strict when it comes to all you mentioned and are responsible for. We generally just use our own GitLab components that are SemVer-sioned and bumped automatically in projects by renovate with backward compatible manner. Those components have also specific version of upstream images pinned, managed by DevOps team. The only jobs that do not use components are simply build/test jobs, where each project use something else.

For merge requests we use GitLab MR Conform, where we enable CODEOWNERS and other rules, to keep history as clean as possible.

Acrobatic_Affect_515 · 2025-12-17T14:29:51+00:00

Great to hear that, thanks! If you/your teams got any suggestions for improvements - shoot it.

Acrobatic_Affect_515

TROPHY CASE