[BUG] failed calling webhook "mcloneset.kb.io": failed to call webhook: Post "https://kruise-webhook-service.kruise-system.svc:443/mutate-apps-kruise-io-v1alpha1-cloneset?timeout=30s": EOF

[xlcbingo1999]

What happened: I got the error as below.

error from server (InternalError): error when creating "/root/test_k8s/kruise/config/samples/apps_v1alpha1_cloneset.yaml": Internal error occurred: failed calling webhook "mcloneset.kb.io": failed to call webhook: Post "https://kruise-webhook-service.kruise-system.svc:443/mutate-apps-kruise-io-v1alpha1-cloneset?timeout=30s": EOF

What you expected to happen: Deploy a sample cloneset normally.

How to reproduce it (as minimally and precisely as possible):

First, I was in default namespace, and used helm to install a new kruise. My install code:

helm install kruise openkruise/kruise --version 1.6.3

Second, I got the success message about install the kruise.

# helm status kruise
NAME: kruise
LAST DEPLOYED: Thu Jun 27 20:55:31 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

Third, I apply a cloneset in default namespace:

apiVersion: apps.kruise.io/v1alpha1
kind: CloneSet
metadata:
  labels:
    app: sample
  name: sample
  namespace: default
spec:
  replicas: 5
  selector:
    matchLabels:
      app: sample
  template:
    metadata:
      labels:
        app: sample
    spec:
      containers:
      - name: main
        image: nginx:alpine
  updateStrategy:
    type: InPlaceIfPossible
    maxUnavailable: 2

Fourth, I got error

error from server (InternalError): error when creating "/root/test_k8s/kruise/config/samples/apps_v1alpha1_cloneset.yaml": Internal error occurred: failed calling webhook "mcloneset.kb.io": failed to call webhook: Post "https://kruise-webhook-service.kruise-system.svc:443/mutate-apps-kruise-io-v1alpha1-cloneset?timeout=30s": EOF

Anything else we need to know?:

Environment:

• Kruise version: 1.6.3
• Kubernetes version (use kubectl version): v1.25.16
• Install details (e.g. helm install args): helm install kruise openkruise/kruise --version 1.6.3
• Others: None

[xlcbingo1999]

I met the same problem when I run the source main.go.

[zmberg]

@xlcbingo1999 Can you show kubectl get ep -n kruise-system and kubectl get pods -n kruise-system

[xlcbingo1999]

@xlcbingo1999 Can you show kubectl get ep -n kruise-system and kubectl get pods -n kruise-system

@zmberg These are the results.

# kubectl get pods -n kruise-system
NAME                                         READY   STATUS    RESTARTS   AGE
kruise-controller-manager-7d595946b6-qcknr   1/1     Running   0          12h
kruise-controller-manager-7d595946b6-zl2xz   1/1     Running   0          12h
kruise-daemon-lmcz7                          1/1     Running   0          12h
kruise-daemon-vq8lb                          1/1     Running   0          12h
kruise-daemon-xvkqm                          1/1     Running   0          12h

# kubectl get ep -n kruise-system
NAME                     ENDPOINTS                           AGE
kruise-webhook-service   10.244.1.72:9876,10.244.3.90:9876   12h

# kubectl describe ep kruise-webhook-service -n kruise-system
Name:         kruise-webhook-service
Namespace:    kruise-system
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  endpoints.kubernetes.io/last-change-trigger-time: 2024-06-27T12:55:54Z
Subsets:
  Addresses:          10.244.1.72,10.244.3.90
  NotReadyAddresses:  <none>
  Ports:
    Name     Port  Protocol
    ----     ----  --------
    <unset>  9876  TCP
Events:  <none>