KubeSphere 3.0 卸载后重装，装不下去

xingye311

如题，前两天已经装过ks3.0,因为流水线的配置有点问题，今天卸载后想重装下，但是执行安装命令：
kubectl apply -f https://raw.githubusercontent.com/kubesphere/ks-installer/v3.0.0-alpha.1/deploy/kubesphere-installer.yaml
后，NAMESPACE 和 deployments 都创建出来了，但是等了半天，ks-installer的pod一直起不来，查看deployment的日志，是这样的：

[root@master1 ~]# kubectl describe deployments  ks-installer  -n kubesphere-system
Name:                   ks-installer
Namespace:              kubesphere-system
CreationTimestamp:      Mon, 13 Jul 2020 10:46:52 +0800
Labels:                 app=ks-install
Annotations:            deployment.kubernetes.io/revision: 1
                        kubectl.kubernetes.io/last-applied-configuration:
                          {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"labels":{"app":"ks-install"},"name":"ks-installer","namespace":"...
Selector:               app=ks-install
Replicas:               1 desired | 0 updated | 0 total | 0 available | 1 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:        kubespheredev/ks-installer:v3.0.0-dev
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:
      /etc/localtime from host-time (rw)
  Volumes:
   host-time:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/localtime
    HostPathType:  
Conditions:
  Type             Status  Reason
  ----             ------  ------
  Available        False   MinimumReplicasUnavailable
  ReplicaFailure   True    FailedCreate
  Progressing      False   ProgressDeadlineExceeded
OldReplicaSets:    <none>
NewReplicaSet:     ks-installer-c588bcbdf (0/1 replicas created)
Events:
  Type    Reason             Age   From                   Message
  ----    ------             ----  ----                   -------
  Normal  ScalingReplicaSet  17m   deployment-controller  Scaled up replica set ks-installer-c588bcbdf to 1`，
  
  再查rs的日志：
  `[root@master1 ~]# kubectl describe rs/ks-installer-c588bcbdf -n kubesphere-system
Name:           ks-installer-c588bcbdf
Namespace:      kubesphere-system
Selector:       app=ks-install,pod-template-hash=c588bcbdf
Labels:         app=ks-install
                pod-template-hash=c588bcbdf
Annotations:    deployment.kubernetes.io/desired-replicas: 1
                deployment.kubernetes.io/max-replicas: 2
                deployment.kubernetes.io/revision: 1
Controlled By:  Deployment/ks-installer
Replicas:       0 current / 1 desired
Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:           app=ks-install
                    pod-template-hash=c588bcbdf
  Service Account:  ks-installer
  Containers:
   installer:
    Image:        kubespheredev/ks-installer:v3.0.0-dev
    Port:         <none>
    Host Port:    <none>
    Environment:  <none>
    Mounts:
      /etc/localtime from host-time (rw)
  Volumes:
   host-time:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/localtime
    HostPathType:  
Conditions:
  Type             Status  Reason
  ----             ------  ------
  ReplicaFailure   True    FailedCreate
Events:
  Type     Reason        Age                   From                   Message
  ----     ------        ----                  ----                   -------
  Warning  FailedCreate  6m10s (x18 over 17m)  replicaset-controller  Error creating: Internal error occurred: failed calling webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: service "istio-sidecar-injector" not found

发现是istio的问题，但是这个已经删除了，怎么处理呢？谢谢

Cauchy

istio是helm部署的，删除的话用helm删，很多组件都是helm部署的。
你现在遇到的这个问题可以删除对应的webhook
kubectl delete mutatingwebhookconfigurations.admissionregistration.k8s.io istio-sidecar-injector

xingye311

Cauchy 执行这个后ks-installer的pod起来了，但是后面还是卡住了，走不下去了，这个是啥问题啊，后面是安装日志：

[root@master1 _]# kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath=‘{.items[0].metadata.name}’) -f
2020-07-13T17:17:02+08:00 INFO : shell-operator v1.0.0-beta.5
2020-07-13T17:17:02+08:00 INFO : HTTP SERVER Listening on 0.0.0.0:9115
2020-07-13T17:17:02+08:00 INFO : Use temporary dir: /tmp/shell-operator
2020-07-13T17:17:02+08:00 INFO : Initialize hooks manager …
2020-07-13T17:17:02+08:00 INFO : Search and load hooks …
2020-07-13T17:17:02+08:00 INFO : Load hook config from ‘/hooks/kubesphere/installRunner.py’
2020-07-13T17:17:03+08:00 INFO : Load hook config from ‘/hooks/kubesphere/schedule.py’
2020-07-13T17:17:03+08:00 INFO : Initializing schedule manager …
2020-07-13T17:17:03+08:00 INFO : KUBE Init Kubernetes client
2020-07-13T17:17:03+08:00 INFO : KUBE-INIT Kubernetes client is configured successfully
2020-07-13T17:17:03+08:00 INFO : MAIN: run main loop
2020-07-13T17:17:03+08:00 INFO : MAIN: add onStartup tasks
2020-07-13T17:17:03+08:00 INFO : MSTOR Create new metric shell_operator_live_ticks
2020-07-13T17:17:03+08:00 INFO : MSTOR Create new metric shell_operator_tasks_queue_length
2020-07-13T17:17:03+08:00 INFO : QUEUE add all HookRun@OnStartup
2020-07-13T17:17:03+08:00 INFO : Running schedule manager …
2020-07-13T17:17:03+08:00 INFO : GVR for kind ‘ClusterConfiguration’ is installer.kubesphere.io/v1alpha1, Resource=clusterconfigurations

xingye311

装好了，是我的疏忽，3.0的还得执行这么一句：
kubectl apply -f https://raw.githubusercontent.com/kubesphere/ks-installer/v3.0.0-alpha.1/deploy/cluster-configuration.yaml
昨天是漏了这个，害