search

kubernetes / minikube

Run Kubernetes locally
https://minikube.sigs.k8s.io/
Apache License 2.0
29.46k stars 4.88k forks source link

Minikube cannot add worker nodes #13616

Closed rakarakhi closed 1 year ago

rakarakhi commented 2 years ago

What Happened?

minikube has many defects:

These needs to be fixed as very high priority.

  1. It is mentioned minikube can create a single node cluster. Very contradicting as there is options to add/remove node.
  2. Adding node to existing cluster does not work. Same behavior in 1.23.1 and 1.25.1
ubuntu@minikube-cluster:~$ minikube version
minikube version: v1.23.1
commit: 84d52cd81015effbdd40c632d9de13db91d48d43

Can create a cluster of 2 nodes

ubuntu@minikube-cluster:~$ minikube start -p minikube-demo --output='text' --nodes 2 --cpus='2' --disk-size='20000mb' --container-runtime='docker' --cni='calico' --cache-images=true --driver='docker' --force-systemd=true --extra-config=kubelet.cgroup-driver=systemd --wait-timeout=6m0s --delete-on-failure=false   --kubernetes-version=v1.21.0 --auto-update-drivers=false --log_file=/home/ubuntu/minikube-start.log --addons=dashboard --addons=metrics-server --addons="ingress" --addons="ingress-dns"
* [minikube-demo] minikube v1.23.1 on Ubuntu 18.04
! Kubernetes 1.21.0 has a known performance issue on cluster startup. It might take 2 to 3 minutes for a cluster to start.
! For more information, see: https://github.com/kubernetes/kubeadm/issues/2395
* minikube 1.25.1 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.25.1
* To disable this notice, run: 'minikube config set WantUpdateNotification false'

* Using the docker driver based on user configuration
* Starting control plane node minikube-demo in cluster minikube-demo
* Pulling base image ...
    > gcr.io/k8s-minikube/kicbase: 355.39 MiB / 355.40 MiB  100.00% 35.88 MiB p
* Creating docker container (CPUs=2, Memory=2200MB) ...
* Preparing Kubernetes v1.21.0 on Docker 20.10.8 ...
  - kubelet.cgroup-driver=systemd
    > kubectl.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s
    > kubelet.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s
    > kubeadm.sha256: 64 B / 64 B [--------------------------] 100.00% ? p/s 0s
    > kubectl: 44.29 MiB / 44.29 MiB [------------] 100.00% 61.59 MiB p/s 900ms
    > kubeadm: 42.56 MiB / 42.56 MiB [-------------] 100.00% 50.06 MiB p/s 1.1s
    > kubelet: 112.59 MiB / 112.59 MiB [-----------] 100.00% 48.24 MiB p/s 2.5s
  - Generating certificates and keys ...
  - Booting up control plane ...
  - Configuring RBAC rules ...
* Configuring Calico (Container Networking Interface) ...
* Verifying Kubernetes components...
  - Using image k8s.gcr.io/ingress-nginx/controller:v1.0.0-beta.3
  - Using image gcr.io/k8s-minikube/minikube-ingress-dns:0.0.1
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  - Using image k8s.gcr.io/metrics-server/metrics-server:v0.4.2
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
  - Using image kubernetesui/metrics-scraper:v1.0.7
  - Using image kubernetesui/dashboard:v2.3.1
* Verifying ingress addon...
* Enabled addons: default-storageclass, storage-provisioner, ingress-dns, metrics-server, dashboard, ingress

* Starting node minikube-demo-m02 in cluster minikube-demo
* Pulling base image ...
* Creating docker container (CPUs=2, Memory=2200MB) ...
* Found network options:
  - NO_PROXY=192.168.49.2
* Preparing Kubernetes v1.21.0 on Docker 20.10.8 ...
  - env NO_PROXY=192.168.49.2
* Verifying Kubernetes components...
* kubectl not found. If you need it, try: 'minikube kubectl -- get pods -A'
* Done! kubectl is now configured to use "minikube-demo" cluster and "default" namespace by default

Please find below result if I try to add 3rd node

ubuntu@minikube-cluster:~$minikube node add -p minikube-demo --delete-on-failure=false --worker=true
* Adding node m03 to cluster minikube-demo
E0215 15:39:02.388286  132023 register.go:141] unexpected first step: ""
* Starting node minikube-demo-m03 in cluster minikube-demo
E0215 15:39:02.390703  132023 register.go:141] unexpected first step: ""
* Pulling base image ...
E0215 15:39:02.518627  132023 register.go:141] unexpected first step: ""
* Creating docker container (CPUs=2, Memory=2200MB) ...\ E0215 15:39:11.364012  132023 register.go:141] unexpected first step: ""
* Preparing Kubernetes v1.21.0 on Docker 20.10.8 ...- E0215 15:41:20.626480  132023 start.go:264] worker node failed to join cluster, will retry: kubeadm join: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.21.0:$PATH kubeadm join control-plane.minikube.internal:8443 --token 0zsxhm.8klcjzz5imp5dy85 --discovery-token-ca-cert-hash sha256:e3c1308c778bc949179fdeb72b04219731046bc32d2b29f38c89df4c940c45b0 --ignore-preflight-errors=all --cri-socket /var/run/dockershim.sock --node-name=minikube-demo-m03": Process exited with status 1
stdout:
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1060-aws
DOCKER_VERSION: 20.10.8
DOCKER_GRAPH_DRIVER: overlay2
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

stderr:
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1060-aws\n", err: exit status 1
        [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher                                                                                                     \ E0215 15:43:38.649869  132023 start.go:264] worker node failed to join cluster, will retry: kubeadm join: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.21.0:$PATH kubeadm join control-plane.minikube.internal:8443 --token 0zsxhm.8klcjzz5imp5dy85 --discovery-token-ca-cert-hash sha256:e3c1308c778bc949179fdeb72b04219731046bc32d2b29f38c89df4c940c45b0 --ignore-preflight-errors=all --cri-socket /var/run/dockershim.sock --node-name=minikube-demo-m03": Process exited with status 1
stdout:
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1060-aws
DOCKER_VERSION: 20.10.8
DOCKER_GRAPH_DRIVER: overlay2
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

stderr:
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1060-aws\n", err: exit status 1
        [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

X Exiting due to K8S_KUBELET_NOT_RUNNING: joining cp: error joining worker node to cluster: kubeadm join: /bin/bash -c "sudo env PATH=/var/lib/minikube/binaries/v1.21.0:$PATH kubeadm join control-plane.minikube.internal:8443 --token 0zsxhm.8klcjzz5imp5dy85 --discovery-token-ca-cert-hash sha256:e3c1308c778bc949179fdeb72b04219731046bc32d2b29f38c89df4c940c45b0 --ignore-preflight-errors=all --cri-socket /var/run/dockershim.sock --node-name=minikube-demo-m03": Process exited with status 1
stdout:
[preflight] Running pre-flight checks
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 5.4.0-1060-aws
DOCKER_VERSION: 20.10.8
DOCKER_GRAPH_DRIVER: overlay2
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
CGROUPS_PIDS: enabled
CGROUPS_HUGETLB: enabled
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: connect: connection refused.

stderr:
        [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
        [WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-1060-aws\n", err: exit status 1
        [WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher

* Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start
* Related issue: https://github.com/kubernetes/minikube/issues/4172
  1. "Suggestion: Check output of 'journalctl -xeu kubelet', try passing --extra-config=kubelet.cgroup-driver=systemd to minikube start" is not relevent and useful as I am not starting a Cluster, adding a node.
  2. The file .minikube/profiles/minikube-demo/config.json has clear reference to cgroup-driver to be systemd, so " [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/" is not very helpful diagnosis.
  3. in the ConfigMap there is no reference to cgroup driver.

Attach the log file

All information is pasted in above screen. In Addition:

kubectl -n kube-system get cm kubeadm-config -o yaml

There is no reference to cgroup driver.

ubuntu@minikube-cluster:~$ kubectl -n kube-system get cm kubeadm-config -o yaml
apiVersion: v1
data:
  ClusterConfiguration: |
    apiServer:
      certSANs:
      - 127.0.0.1
      - localhost
      - 192.168.49.2
      extraArgs:
        authorization-mode: Node,RBAC
        enable-admission-plugins: NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota
      timeoutForControlPlane: 4m0s
    apiVersion: kubeadm.k8s.io/v1beta2
    certificatesDir: /var/lib/minikube/certs
    clusterName: mk
    controlPlaneEndpoint: control-plane.minikube.internal:8443
    controllerManager:
      extraArgs:
        allocate-node-cidrs: "true"
        leader-elect: "false"
    dns:
      type: CoreDNS
    etcd:
      local:
        dataDir: /var/lib/minikube/etcd
        extraArgs:
          proxy-refresh-interval: "70000"
    imageRepository: k8s.gcr.io
    kind: ClusterConfiguration
    kubernetesVersion: v1.21.0
    networking:
      dnsDomain: cluster.local
      podSubnet: 10.244.0.0/16
      serviceSubnet: 10.96.0.0/12
    scheduler:
      extraArgs:
        leader-elect: "false"
  ClusterStatus: |
    apiEndpoints:
      minikube-demo:
        advertiseAddress: 192.168.49.2
        bindPort: 8443
    apiVersion: kubeadm.k8s.io/v1beta2
    kind: ClusterStatus
kind: ConfigMap
metadata:
  creationTimestamp: "2022-02-15T14:52:55Z"
  name: kubeadm-config
  namespace: kube-system
  resourceVersion: "211"
  uid: a047c9db-2e89-4b24-97cc-25d34e6b1ab9
ubuntu@minikube-cluster:~$

Operating System

Ubuntu

Driver

Docker

rakarakhi commented 2 years ago 
ubuntu@minikube-cluster:~$ minikube node list -p minikube-demo
minikube-demo   192.168.49.2
minikube-demo-m02       192.168.49.3
minikube-demo-m03       192.168.49.4
ubuntu@minikube-cluster:~$ minikube status -p minikube-demo
minikube-demo
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

minikube-demo-m02
type: Worker
host: Running
kubelet: Running

minikube-demo-m03
type: Worker
host: Running
kubelet: Stopped

ubuntu@minikube-cluster:~$

deleted minikube and started with nodes=3

ubuntu@minikube-cluster:~$ minikube start -p minikube-demo --output='text' --nodes 3 --cpus='2' --disk-size='20000mb' --container-runtime='docker' --cni='calico' --cache-images=true --driver='docker' --force-systemd=true --extra-config=kubelet.cgroup-driver=systemd --wait-timeout=6m0s --delete-on-failure=false   --kubernetes-version=v1.22.1 --auto-update-drivers=false --log_file=/home/ubuntu/minikube-start.log --addons=dashboard --addons=metrics-server --addons="ingress" --addons="ingress-dns"
* [minikube-demo] minikube v1.23.1 on Ubuntu 18.04
* minikube 1.25.1 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.25.1
* To disable this notice, run: 'minikube config set WantUpdateNotification false'

* Using the docker driver based on user configuration
* Starting control plane node minikube-demo in cluster minikube-demo
* Pulling base image ...
* Downloading Kubernetes v1.22.1 preload ...
    > preloaded-images-k8s-v13-v1...: 511.84 MiB / 511.84 MiB  100.00% 49.00 Mi
* Creating docker container (CPUs=2, Memory=2200MB) ...
* Preparing Kubernetes v1.22.1 on Docker 20.10.8 ...
  - kubelet.cgroup-driver=systemd
  - Generating certificates and keys ...
  - Booting up control plane ...
  - Configuring RBAC rules ...
* Configuring Calico (Container Networking Interface) ...
* Verifying Kubernetes components...
  - Using image k8s.gcr.io/metrics-server/metrics-server:v0.4.2
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  - Using image k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.0
  - Using image k8s.gcr.io/ingress-nginx/controller:v1.0.0-beta.3
  - Using image gcr.io/k8s-minikube/storage-provisioner:v5
  - Using image kubernetesui/dashboard:v2.3.1
  - Using image kubernetesui/metrics-scraper:v1.0.7
  - Using image gcr.io/k8s-minikube/minikube-ingress-dns:0.0.1
* Verifying ingress addon...
* Enabled addons: ingress-dns, storage-provisioner, default-storageclass, metrics-server, dashboard, ingress

* Starting node minikube-demo-m02 in cluster minikube-demo
* Pulling base image ...
* Creating docker container (CPUs=2, Memory=2200MB) ...
* Found network options:
  - NO_PROXY=192.168.49.2
* Preparing Kubernetes v1.22.1 on Docker 20.10.8 ...
  - env NO_PROXY=192.168.49.2
* Verifying Kubernetes components...

* Starting node minikube-demo-m03 in cluster minikube-demo
* Pulling base image ...
* Creating docker container (CPUs=2, Memory=2200MB) ...
* Found network options:
  - NO_PROXY=192.168.49.2,192.168.49.3
* Preparing Kubernetes v1.22.1 on Docker 20.10.8 ...
  - env NO_PROXY=192.168.49.2
  - env NO_PROXY=192.168.49.2,192.168.49.3
* Verifying Kubernetes components...
* Done! kubectl is now configured to use "minikube-demo" cluster and "default" namespace by default
ubuntu@minikube-cluster:~$
ubuntu@minikube-cluster:~$
ubuntu@minikube-cluster:~$
ubuntu@minikube-cluster:~$ sudo apt-get upgrade -y kubectl=1.22.1-00
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  kubectl
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 9036 kB of archives.
After this operation, 471 kB of additional disk space will be used.
Get:1 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 kubectl amd64 1.22.1-00 [9036 kB]
Fetched 9036 kB in 1s (16.9 MB/s)
(Reading database ... 85987 files and directories currently installed.)
Preparing to unpack .../kubectl_1.22.1-00_amd64.deb ...
Unpacking kubectl (1.22.1-00) over (1.21.0-00) ...
Setting up kubectl (1.22.1-00) ...
ubuntu@minikube-cluster:~$
ubuntu@minikube-cluster:~$ minikube status -p minikube-demo
minikube-demo
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

minikube-demo-m02
type: Worker
host: Running
kubelet: Running

minikube-demo-m03
type: Worker
host: Running
kubelet: Running

ubuntu@minikube-cluster:~$
rakarakhi commented 2 years ago
  1. I have provided adequate information and workaround.
  2. Now I have a 3 node cluster which will suffice my purpose.
  3. At your end kindly triage, put appropriate labels and fixe the mentioned issue

This is my humble request to the minikube community. If you need any additional information, I will share gladly.

afbjorklund commented 2 years ago

It is mentioned minikube can create a single node cluster.

Where is this mention ?

rakarakhi commented 2 years ago

I will check and let you know.

Thanks a lot for your time and support.

Regards,

Rahuldeb Chakrabarty

Email: @.*** Mobile: +91 98660 70127 https://www.linkedin.com/in/RahuldebChakrabartyIITB

On Tue, Feb 15, 2022 at 10:58 PM Anders Björklund @.***> wrote:

It is mentioned minikube can create a single node cluster.

Where is this mention ?

— Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/13616#issuecomment-1040564184, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGZLL47BUOPLT53XE7UP2ATU3KEMBANCNFSM5OPB3MEA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

sharifelgamal commented 2 years ago

We have integration tests on several different platform/driver combinations that do exactly this and pass, so I'm not sure where your issue stems from exactly, I imagine it has something to do with your specific minikube setup. I'd try updating the version of minikube and kubernetes and see if that helps anything.

fujiawei-dev commented 2 years ago

I have the same trouble.

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/13616#issuecomment-1339707669): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.