CRAYSAT-1857:bootsys stage to wait for kyverno before job recreation #225
Conversation
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
IM:CRAYSAT-1857 Reviewer:Ryan Updating boot platform-services stage to wait for kyverno avaiability before going to recreate cronjob stage
shivaprasad-metimath
force-pushed
the
CRAYSAT-1857-bootsys-cronjob-creation-failure
branch
from
d33131b to
f586922
Compare
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
IM:CRAYSAT-1857
Reviewer:Ryan
Summary and Scope
Updating sat boot platform-services stage to wait for kyverno availability before going to recreate cronjob stage to avoid the warnings.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
List the environments in which these changes were tested.
Tested on:
Test description:
Will perform the shutdown and boot activity to verify the platform-services output to validate the changes effectiveness.
Risks and Mitigations
low
Pull Request Checklist