Deckhouse Kubernetes Platform in existing cluster

• Error of the following kind:

  │ │ ┌ Waiting for Deckhouse to become Ready
  │ │ │ Deckhouse pod found: deckhouse-64649df6f9-mf6dt (Pending)
  │ │ │ Deckhouse pod found: deckhouse-64649df6f9-mf6dt (Pending)
  

  Probably, there is no node in the cluster with the node-role.kubernetes.io/control-plane: "" label which is originally used in the nodeSelector of the deckhouse deployment manifest.

  Ways to fix the error:

  • Insert the proper nodeSelector into the deckhouse deployment:

    kubectl -n d8-system edit deployment/deckhouse
    

  • Delete nodeSelector in the deckhouse deployment:

    kubectl patch -n d8-system deployment deckhouse --type json -p '[{"op": "remove", "path": "/spec/template/spec/nodeSelector"}]'
    

• Error of the following kind:

  Waiting for Deckhouse to become Ready
  │ │ Deckhouse pod found: deckhouse-7cc8b6f4bd-9l99t (Running)
  │ │ Running pod found! Checking logs...
  │ │ Request failed. Probably pod was restarted during installation.
  │ │ No Deckhouse pod found.
  

  And also an error with the status appears in the deckhouse module:

  Status:   ModuleError: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "system-ns.deckhouse.io" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "label-objects.deckhouse.io" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicy" in version "admissionregistration.k8s.io/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "system-ns.deckhouse.io" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1" ensure CRDs are installed first, resource mapping not found for name: "heritage-label-objects.deckhouse.io" namespace: "" from "": no matches for kind "ValidatingAdmissionPolicyBinding" in version "admissionregistration.k8s.io/v1beta1" ensure CRDs are installed first]
  

  May be, the kube-apiserver.yaml static manifest does not specify `runtime-config’.

  Add the spec.containers.command parameter to /etc/kubernetes/manifests/kube-api server.yaml value- –runtime-config=admissionregistration.k8s.io/v1beta1=true,admissionregistration.k8s.io/v1alpha1=true`.

  Caution. kube-apiserver may not respond to requests for a while.

If the Deckhouse installation was interrupted for unknown reasons, the following error may be displayed during the re-installation:

  ┌ ⛵ ~ Bootstrap: Install Deckhouse
  └ ⛵ ~ Bootstrap: Install Deckhouse (43.50 seconds) FAILED

  Timeout while "Check prevent break another bootstrapped": last error: Cluster UUID's not equal in the cluster                              ↵
  (7489d07a-5fbb-4269-ba0d-e0340ce4f118) and in the cache ().
  Probably you are trying bootstrap cluster on node with previous created cluster.
  Please check hostname.

To reinstall Deckhouse on the cluster, you need to delete the following ConfigMaps in the namespace kube-system:

  d8-cluster-is-bootstraped
  d8-cluster-uuid

and then start the installation again.

The documentation module (deckhouse-web in Deckhouse 1.45 or older), which provides a web interface to the cluster documentation, requires the Ingress controller to be active in the cluster. If there is no Ingress controller in your cluster, you can use the built-in ingress-nginx module:

• Enable the ingress-nginx module, by executing the following command:

  Copy content

  kubectl create -f - <<EOF
  apiVersion: deckhouse.io/v1alpha1
  kind: ModuleConfig
  metadata:
    name: ingress-nginx
  spec:
    enabled: true
  EOF
  

  kubectl create -f - <<EOF apiVersion: deckhouse.io/v1alpha1 kind: ModuleConfig metadata: name: ingress-nginx spec: enabled: true EOF

• Create an ingress-nginx-controller.yml file with the following contents:

  ingress-nginx-controller.ymlCopy filenameCopy content

  # Section containing the parameters of NGINX Ingress controller.
  # https://deckhouse.io/products/kubernetes-platform/documentation/v1/modules/402-ingress-nginx/cr.html
  apiVersion: deckhouse.io/v1
  kind: IngressNginxController
  metadata:
    name: nginx
  spec:
    ingressClass: nginx
    # The way traffic goes to cluster from the outer network.
    inlet: HostPort
    hostPort:
      httpPort: 80
      httpsPort: 443
    # Describes on which nodes the component will be located.
    # You might consider changing this.
    nodeSelector:
      node-role.kubernetes.io/control-plane: ""
    tolerations:
    - operator: Exists
  

  # Section containing the parameters of NGINX Ingress controller. # https://deckhouse.io/products/kubernetes-platform/documentation/v1/modules/402-ingress-nginx/cr.html apiVersion: deckhouse.io/v1 kind: IngressNginxController metadata: name: nginx spec: ingressClass: nginx # The way traffic goes to cluster from the outer network. inlet: HostPort hostPort: httpPort: 80 httpsPort: 443 # Describes on which nodes the component will be located. # You might consider changing this. nodeSelector: node-role.kubernetes.io/control-plane: "" tolerations: - operator: Exists

• Once Deckhouse is installed, apply the file using the command below:

  Copy content

  kubectl create -f ingress-nginx-controller.yml
  

  kubectl create -f ingress-nginx-controller.yml