John Gardiner Myers

/remove-lifecycle rotten I also ran into this. A service had changed the names of containers and volumes and that apply had gotten rolled back. Upon rolling forward again, the old...

Reproduction procedure: ```shell cat >sample.yaml

@pacoxu your comment does not address the issue as described. This is about `kubectl.kubernetes.io/last-applied-configuration`, not `kubernetes.io/change-cause`.

/kind bug /remove-kind feature

In the current behavior, after a `kubectl rollout undo` the `kubectl.kubernetes.io/last-applied-configuration` refers to a configuration that is no longer the last applied. As I have demonstrated, the current behavior causes...

If `kubectl rollout undo` is not intended to work with `kubectl apply` then it should remove `kubectl apply`'s annotation, not leave it in an incorrect state.

How would an imperative workflow configure a resource that could then safely be targeted by `rollout undo`, if not with `apply`?

> Unfortunately that would exacerbate the problem for the users this affects, since the result would be apply not owning any of the fields it previously did as of the...

@KaibaLopez in service/ec2/api.go around line 116742, the second sentence is incorrect.: ``` // The type of hostnames to assign to instances in the subnet at launch. For // IPv4 only...

It's easier to add packages to a base than remove them.