Skip to content

Conversation

@YuryHrytsuk
Copy link
Collaborator

@YuryHrytsuk YuryHrytsuk commented Oct 28, 2025

What do these changes do?

All resources that rely on cert-manager CRDs should be installed after

  1. CRDs are installed (achieved via helm.sh/hook: post-install,post-upgrade)
  2. webhook server is ready to accept connections (achieved via
    helm.sh/hook-weight: "10" which makes it wait until startupapicheck
    job is completed aka cert-manager is ready)

Related issue/s

cert-manager related:

Related PR/s

Checklist

  • I tested and it works

All resources that rely on `cert-manager` CRDs should be installed after
1) CRDs are installed (achieved via `helm.sh/hook:
   post-install,post-upgrade`)
2) webhook server is ready to accept connections (achieved via
   `helm.sh/hook-weight: "10"` which makes it wait until startupapicheck
job is completed aka `cert-manager` is ready)

Related issue/s
* closes ITISFoundation#1241
@YuryHrytsuk YuryHrytsuk added this to the Imparable milestone Oct 28, 2025
@YuryHrytsuk YuryHrytsuk self-assigned this Oct 28, 2025
Copy link
Member

@mrnicegyu11 mrnicegyu11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx!

@YuryHrytsuk YuryHrytsuk merged commit 3e9806d into ITISFoundation:main Oct 29, 2025
3 checks passed
@YuryHrytsuk YuryHrytsuk deleted the kubernetes-fix-cert-manager-first-installation branch October 29, 2025 07:46
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.

Kubernetes: install cert-manager from scratch is broken

2 participants