[FLINK-36513][ci] Storing the cert-manager.yaml to avoid downloading timeout #897
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
Contributor
|
I generally would prefer storing the yaml in our code base if that’s possible to avoid this but if you like this approach more then good to go from my end :) |
1996fanrui
force-pushed
the
36513/retry-Install-cert-manager
branch
from
93ac39e to
6d8b60e
Compare
1996fanrui
changed the title
kubectl apply cert-manager
gyfora
approved these changes
Oct 12, 2024
Member
Author
|
Thank you for the quick review, merging~ |
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.
What is the purpose of the change
A lot of CI failures are caused by Install cert-manager. Get more details from FLINK-36513.
Brief change log
[FLINK-36513][ci] Storing the cert-manager.yaml to avoid downloading timeout
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
CustomResourceDescriptors: noDocumentation