Skip to content

charts/gitlab-ci-pipelines-exporter: secret naming and redis resources (0.3.6)#90

Open
laimis9133 wants to merge 2 commits into
mvisonneau:mainfrom
laimis9133:correct-secret-naming
Open

charts/gitlab-ci-pipelines-exporter: secret naming and redis resources (0.3.6)#90
laimis9133 wants to merge 2 commits into
mvisonneau:mainfrom
laimis9133:correct-secret-naming

Conversation

@laimis9133

@laimis9133 laimis9133 commented Apr 29, 2025

Copy link
Copy Markdown

This PR is to change the secret naming for gitlab-ci-pipelines-exporter/templates/secret.yaml from the current {{ template "app.fullname" . }}-config to {{ template "app.fullname" . }}-secret.

The current setup brings back Warnings for users using the Helm chart with ArgoCD deployments: RepeatedResourceWarning - Resource /ConfigMap/monitoring/gitlab-ci-pipelines-exporter-config appeared 2 times among application resources. This change also follows the naming convention for Kubernetes resources/objects that are consistent across the chart.

Redis resource configuratino has also been added as for large GitLab instances the default values are often too small for usage.

An additional minute change is for the GitLab URL link in the commet section adding a trailing slash in the end. Some users have encountered Readiness probe HTTP 503 errors when setting up and a more specific example might be helpful.

Make tests for docs, lint and kubeconform completed. Chart version bumped to 0.3.6 as well.

Correct secret naming from -config to -secret.
Add trailing slash for GitLab URL in the comment example.

Signed-off-by: Laimis Juzeliunas <asnelaimis@gmail.com>
Adding Redis resource configuration to the chart.
@laimis9133 laimis9133 changed the title charts/gitlab-ci-pipelines-exporter: correct secret naming (0.3.6) charts/gitlab-ci-pipelines-exporter: secret naming and redis resources (0.3.6) May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant