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
When I load image from centos:8 -> centos:7, and the two images exist on all nodes in the cluster.
We can find four pods with InPlaceUpdateReady =False conditions.
When we remove the 'example.io/unready-inplaceupdate-blocker' tag, after a while we can see that the pod is ready, but the rest of the pod has not been updated
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Kruise version: 1.6.0
Kubernetes version (use kubectl version):
Cluster installed with kind
Client Version: v1.29.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.24.15
WARNING: version difference between client (1.29) and server (1.24) exceeds the supported minor version skew of +/-1
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):helm install kruise openkruise/kruise --version 1.6.0 --set manager.image.repository=openkruise-registry.cn-shanghai.cr.aliyuncs.com/openkruise/kruise-manager
Operation procedure
k apply -f sa.yaml
change image
k apply -f sa.yaml
The text was updated successfully, but these errors were encountered: