[CHORE] enforcing default value instead of block cr onboarding #136
Conversation
This file contains 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
Coverage provided by https://github.com/seriousben/go-patch-cover-action |
Signed-off-by: Nicolas Takashi <nicolas.takashi@coralogix.com>
nicolastakashi
force-pushed
the
chore/enforce-interval-instead-of-blocking-on-cr
branch
from
c04ee7f
to
14578d3
Compare
OrNovo
approved these changes
Aug 26, 2024
nicolastakashi
deleted the
chore/enforce-interval-instead-of-blocking-on-cr
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enforcing default interval is a better approach in this case than block on CRD, since some customers might have generate prometheus rules being created by third part service that don't allow rule interval configuration.