*Created by: pcgeek86* **General remarks** > This form is to report bugs. For general usage questions refer to our Slack channel > [KubeSphere-users](https://join.slack.com/t/kubesphere/shared_invite/enQtNTE3MDIxNzUxNzQ0LTdkNTc3OTdmNzdiODViZjViNTU5ZDY3M2I2MzY4MTI4OGZlOTJmMDg5ZTFiMDAwYzNlZDY5NjA0NzZlNDU5NmY) **Describe the bug** - I am being blocked from proceeding in the KubeSphere console by a webhook-related bug. - I created a k8s cluster on Amazon EKS, using `eksctl`. - I deployed KubeSphere using the k8s manifest files in the documentation. - Then I changed the `ks-console` service type to `LoadBalancer`. - Then I tried to login to the console through the load balancer's external DNS name. <img width="425" alt="Screen Shot 2022-02-28 at 10 39 04 AM" src="https://user-images.githubusercontent.com/466713/156031474-6fe0f06c-f9cb-4179-a96b-24dceb040b90.png"> ``` ubuntu@vm01:~$ kubectl get all --namespace kubesphere-system NAME READY STATUS RESTARTS AGE pod/ks-apiserver-55d68bd7f-75nqm 1/1 Running 0 5m16s pod/ks-console-65f4d44d88-hmhp8 1/1 Running 0 19m pod/ks-controller-manager-68b54f7967-rg99p 1/1 Running 0 5m16s pod/ks-installer-85dcfff87d-tt5cq 1/1 Running 0 9m51s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ks-apiserver ClusterIP 10.100.228.188 <none> 80/TCP 19m service/ks-console LoadBalancer 10.100.232.102 a94291894669b4059b67eaad7cc534be-1183942353.us-west-2.elb.amazonaws.com 80:30880/TCP 19m service/ks-controller-manager ClusterIP 10.100.12.182 <none> 443/TCP 19m NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/ks-apiserver 1/1 1 1 19m deployment.apps/ks-console 1/1 1 1 19m deployment.apps/ks-controller-manager 1/1 1 1 19m deployment.apps/ks-installer 1/1 1 1 68m NAME DESIRED CURRENT READY AGE replicaset.apps/ks-apiserver-55d68bd7f 1 1 1 5m16s replicaset.apps/ks-apiserver-69b77996db 0 0 0 19m replicaset.apps/ks-apiserver-6bcd4675f9 0 0 0 5m30s replicaset.apps/ks-apiserver-6f48b8598 0 0 0 15m replicaset.apps/ks-apiserver-dccc7546 0 0 0 16m replicaset.apps/ks-console-65f4d44d88 1 1 1 19m replicaset.apps/ks-controller-manager-5785c696df 0 0 0 16m replicaset.apps/ks-controller-manager-5f89b68b7d 0 0 0 19m replicaset.apps/ks-controller-manager-64b88f6dc8 0 0 0 15m replicaset.apps/ks-controller-manager-66fd555c4 0 0 0 5m29s replicaset.apps/ks-controller-manager-68b54f7967 1 1 1 5m16s replicaset.apps/ks-installer-85dcfff87d 1 1 1 68m ``` **Versions used(KubeSphere/Kubernetes)** KubeSphere: see below Kubernetes: 1.21.5 EKS ``` Name: ks-installer Namespace: kubesphere-system CreationTimestamp: Mon, 28 Feb 2022 16:27:34 +0000 Labels: app=ks-install Annotations: deployment.kubernetes.io/revision: 1 Selector: app=ks-install Replicas: 1 desired | 1 updated | 1 total | 1 available | 0 unavailable StrategyType: RollingUpdate MinReadySeconds: 0 RollingUpdateStrategy: 25% max unavailable, 25% max surge Pod Template: Labels: app=ks-install Service Account: ks-installer Containers: installer: Image: kubesphere/ks-installer:v3.2.1 Port: <none> Host Port: <none> Limits: cpu: 1 memory: 1Gi Requests: cpu: 20m memory: 100Mi Environment: <none> Mounts: /etc/localtime from host-time (ro) Volumes: host-time: Type: HostPath (bare host directory volume) Path: /etc/localtime HostPathType: Conditions: Type Status Reason ---- ------ ------ Progressing True NewReplicaSetAvailable Available True MinimumReplicasAvailable OldReplicaSets: <none> NewReplicaSet: ks-installer-85dcfff87d (1/1 replicas created) Events: <none> ``` **Environment** How many nodes and their hardware configuration: For example: EKS master 2 nodes: 8cpu/16g (and other info are welcomed to help us debugging) **To Reproduce** See above. **Expected behavior** I should be able to change password or skip changing password, so I can login to KubeSphere Console.