You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Following the steps in quick start. Tried several k8s such as minikube, kind and EKS, always got this error
cannot find sts/apiserver in ns default-31ceae-vc-sample-1: default-31ceae-vc-sample-1/apiserver is not ready in 120 seconds
What did you expect to happen:
The virtual cluster should be created successfully
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
My kubectl, minikube, kind are all of the latest version
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Following the steps in quick start. Tried several k8s such as minikube, kind and EKS, always got this error
cannot find sts/apiserver in ns default-31ceae-vc-sample-1: default-31ceae-vc-sample-1/apiserver is not ready in 120 seconds
What did you expect to happen:
The virtual cluster should be created successfully
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
My kubectl, minikube, kind are all of the latest version
Environment:
minikube: 1.23.2
kind: 0.11
kubectl:1.22
kubectl version
):/etc/os-release
):/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-provider-nested/labels?q=area for the list of labels]
The text was updated successfully, but these errors were encountered: