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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Surface cpu and mem requests forbidden errors (and other ones too) in KSVC creation #14453
Surface cpu and mem requests forbidden errors (and other ones too) in KSVC creation #14453
Changes from all commits
933ff82
da77117
97a75c2
f2a37f5
4c39ae2
caf0d9e
d921741
158d35b
5ff10f6
25714c2
2b999c8
b02331f
d061fe7
7d2d707
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My initial thought was to have this in the
else
clause. But seeing this here I wonder if there is a case where creating the Deployment will succeed but response includes a status condition with a ReplicaFailure?Otherwise this section might be easier to reason about if we push
if !rev.Status.IsActivationRequired()
down intoPropagateDeploymentStatus
and we can do the replica failure check thereThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that I revisit the code, yes the reason to have it there is for newly created deployments with replicaset errors.
I couldn't move it inside propagate status inside since they are both different cases. The revision required surface an error but it does not care to be overwritten later, and you can have a replicaset error without a replicaset error, with the replicaset error we want to return immediately after so we need to check in the reconciler.