Fix ArgoCD bootstrap blocked by missing espejote CRDs#298
Open
haasad wants to merge 2 commits into
Open
Conversation
|
🚀 Merging this PR will release Merging will trigger workflows 🛠️ Auto tagging enabled with label |
haasad
force-pushed
the
fix/4.21-bootstrap
branch
from
976b73b to
0c2f8aa
Compare
bastjan
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
During the setup of a fresh OpenShift 4.21 cluster we discovered that the new espejote admission to set the priority class blocks the ArgoCD bootstrap, because the espejote CRDs are not yet available.
This PR sets the
SkipDryRunOnMissingResource=truesync option for the whole argocd application to prevent sync errors, also for similar cases in the future. We also add a higher sync wave for the espejote admission to ensure that the syn argocd instance is created first.Checklist
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
bug,enhancement,documentation,change,breaking,dependencyas they show up in the changelog.