Skip to content

Conversation

@YuryHrytsuk
Copy link
Collaborator

What do these changes do?

Wait for calico api resources to initialize before announcing local cluster is ready. Waiting for calico pods to start was not enough.

Related issue/s

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
Wait for calico api resources to initialize before announcing local cluster is
ready. Waiting for calico pods to start was not enough.
@YuryHrytsuk YuryHrytsuk added this to the Imparable milestone Oct 29, 2025
@YuryHrytsuk YuryHrytsuk self-assigned this Oct 29, 2025
@YuryHrytsuk YuryHrytsuk merged commit b1530ad into ITISFoundation:main Oct 29, 2025
3 checks passed
@YuryHrytsuk YuryHrytsuk deleted the kubernetes-local-cluster-wait-to-init branch October 29, 2025 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant