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
istioctl x kube-uninject doesn't restore probes (liveness e readiness).
Try this:
Create a deployment with 1 or 2 containers
In each container, configure a livenessProbe and readnessProbe configuration
Inject the proxy with kubectl get deploy $DEPLOY | istioctl kube-inject -f - | kubectl apply -f -
Now try to uninject the proxy with: kubectl get deploy $DEPLOY | istioctl x kube-uninject -f - | kubectl apply -f -
Note that when I inject the istio-proxy it will create a new container, and the proxy will hold an env ISTIO_KUBE_APP_PROBERS having the real probes.
Now the problem, when the kube-uninject is ran it will not restore the original probes from that env ISTIO_KUBE_APP_PROBERS and will keep the old ones on app containers ( ex.: /app-health/container_name/readyz and /app-health/container_name/livez ).
Lets see an example:
This is how the containers probes are been keeped after the kube-inject and kube-uninject:
$ istioctl version
client version: 1.14.5
control plane version: 1.14.5
data plane version: 1.14.5 (3 proxies)
$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.24.12
Kustomize Version: v4.5.4
Server Version: v1.24.13
Additional Information
No response
Affected product area
Ambient
Docs
Installation
Networking
Performance and Scalability
Extensions and Telemetry
Security
Test and Release
User Experience
Developer Infrastructure
Upgrade
Multi Cluster
Virtual Machine
Control Plane Revisions
The text was updated successfully, but these errors were encountered:
Bug Description
istioctl x kube-uninject
doesn't restore probes (liveness e readiness).Try this:
livenessProbe
andreadnessProbe
configurationkubectl get deploy $DEPLOY | istioctl kube-inject -f - | kubectl apply -f -
kubectl get deploy $DEPLOY | istioctl x kube-uninject -f - | kubectl apply -f -
Note that when I inject the
istio-proxy
it will create a new container, and the proxy will hold an envISTIO_KUBE_APP_PROBERS
having the real probes.Now the problem, when the
kube-uninject
is ran it will not restore the original probes from that envISTIO_KUBE_APP_PROBERS
and will keep the old ones on app containers ( ex.:/app-health/container_name/readyz
and/app-health/container_name/livez
).Lets see an example:
This is how the containers probes are been keeped after the
kube-inject
andkube-uninject
:And here is the probes that I expected to be restored from proxy env
ISTIO_KUBE_APP_PROBERS
after thekube-uninject
ran:Version
Additional Information
No response
Affected product area
The text was updated successfully, but these errors were encountered: