Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stackspin stackspin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 148
    • Issues 148
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • stackspinstackspin
  • stackspinstackspin
  • Issues
  • #1060
Closed
Open
Issue created Nov 30, 2021 by Varac@varacContributor

Only use zerossl in CI

This is a follow-up of #1059 (closed), which fixed the ZeroSSL clusterIssuer registration.

I realized that the co-existence of LE and zerossl clusterIssuer will lead to unwanted consequences: Whenever the (default) zerossl clusterIssuer is unavailable the LE clusterIssuer is used as fallback. So we end up with LE certs which we want to avoid.

So we need to find a way to disable/don't install the LE issuer.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking