Page MenuHomeSoftware Heritage

gitlab-staging: Add the configuration to install the gitlab operator
ClosedPublic

Authored by vsellier on Oct 6 2022, 11:03 AM.

Details

Summary

It prepares the configuration to install the production environment

Related to T4063

Diff Detail

Repository
rSKCONF Kubernetes clusters configuration
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

vsellier created this revision.
This revision is now accepted and ready to land.Oct 6 2022, 11:59 AM
olasd added inline comments.
argocd/applications/gitlab-staging/cert-manager-application.yaml
22

This seems inconsistent with the --version v1.8.0 above. Which is right?

argocd/applications/gitlab-staging/cert-manager-application.yaml
22

This one is the good one, I took the opportunity to upgrade cert-manager.
I will remove the comment, it adds nothing.

Well to be exact, during the tests I partially deployed the 1.9.1. The new crds was applied.
At this point, I had 2 possibilities: clean everything and reinstall the 1.8.0 or finalize the 1.9.1 installation.

I chose the 2d choice ;)

argocd/applications/gitlab-staging/cert-manager-application.yaml
22

I meant that the CLI had v1.8.0, and your manifest doesn't have the v. But if it works, it works :-)

argocd/applications/gitlab-staging/cert-manager-application.yaml
22

heh good point.
It Looks like both are working because if the version is not found, helm is searching for a tag in the repository which is 1.9.1, the real version is well v1.9.1 so I will update it

  • fix the version number
  • remove the command line in comment