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.
Please note this is not a final PR. Just open this for a discussion.
When we use
kubectl apply
to create resource, we update the annotation, add thelast-applied-configuration
. But thislast-applied-configuration
is not the real configuration we used to create the resource, it's just read from the command input. e.g:Create a deployment with
apply -f
:The
last-applied-configuration
would be:but the real configuration sent to apiserver would be:
The
last-applied-configuration
annotation has no fields which we set by default. I think this has leads some bugs for apply usage.