You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been adding the linkerd injection via fluxcd's HelmReleases and sometimes passed the inject in with operators. In order to upgrade linkerd and also have it continue to be controlled by fluxcd, I needed to migrate to the new helmreleases in flux with the new split charts in 2.12. Anyway, I tried to run some objects thru uninject and kubectl apply and got warnings about last-applied-configuration. The annotation change would not get picked up. Sometimes it was because an operator was controlling the object but other times it wasn't. I tried changing to server-side-apply with no improvement, but doing akubectl edit on the object and removing the annotation by hand did pick up the change, as well as doing kubectl patch to change the annotation.
Is kubectl apply still the best way to go about uninstalling? If so, it seems like there is potential to improve the user experience by detecting of the lack of the last-applied-config annotation to warn the user that something else may have injected linkerd originally.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been adding the linkerd injection via fluxcd's HelmReleases and sometimes passed the inject in with operators. In order to upgrade linkerd and also have it continue to be controlled by fluxcd, I needed to migrate to the new helmreleases in flux with the new split charts in 2.12. Anyway, I tried to run some objects thru
uninject
andkubectl apply
and got warnings about last-applied-configuration. The annotation change would not get picked up. Sometimes it was because an operator was controlling the object but other times it wasn't. I tried changing to server-side-apply with no improvement, but doing akubectl edit
on the object and removing the annotation by hand did pick up the change, as well as doingkubectl patch
to change the annotation.Is
kubectl apply
still the best way to go about uninstalling? If so, it seems like there is potential to improve the user experience by detecting of the lack of the last-applied-config annotation to warn the user that something else may have injected linkerd originally.Beta Was this translation helpful? Give feedback.
All reactions