cluster-api-provider-nested: VirtualCluster fail to create with "cannot find sts/apiserver in ns" on minikube running k8s 1.20.2

The VirtualCluster fail to create the apiserver and the apiserver-0 is in the container creating state kubectl-vc create -f virtualcluster_1_nodeport.yaml -o vc.kubeconfig 2021/07/28 08:20:03 etcd is ready cannot find sts/apiserver in ns default-e4d075-vc-sample-1: default-e4d075-vc-sample-1/apiserver is not ready in 120 seconds

kubectl get po -n default-e4d075-vc-sample-1 NAME READY STATUS RESTARTS AGE apiserver-0 0/1 ContainerCreating 0 46m etcd-0 1/1 Running 1 47m

What steps did you take and what happened: Followed the step as per the virtual cluster walkthrough demo and all the steps were successful till the Create VirtualCluster.
https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/doc/demo.md

During the Create VirtualCluster the etcd came up fine but the apiserver-0 stayed in the ContainerCreating state.

What did you expect to happen: Expected to see the apiserver and controller-manager to be in running state.

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • cluster-api-provider-nested version:
  • Minikube/KIND version: minikube version: v1.21.0
  • Kubernetes version: (use kubectl version): 1.20.2
  • OS (e.g. from /etc/os-release): darwin

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

@sriram-kannan-infoblox as a workaround, please remove the aggregate api support, check https://github.com/kubernetes-sigs/cluster-api-provider-nested/pull/167/files for how to remove, you only need to update the statefulset for apiserver.

The https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/doc/demo.md need some update, as it is not using the latest image.

apiserver-0 0/1 ContainerCreating 0 46m

what’s the reason for this creating status? I ecountered this before due to docker pull limit but seems you are not, how about check the reason for why container creating in 46 min? e.g describe the container for additional info?