-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The pod is always pending in the nested cluster #156
Comments
Hey @wangjsty this is expected right now, we haven't finished the integration updates to immediately support CAPN + VC, the doc updates should be mostly called out in #141. Which is blocked on updating VC to support the way we're releasing images and manifests w/ CAPN/Prow. |
Yes. At this moment, for VC demo, you can try the following demo which use the old clusterversion CR unless your purpose is to try CAPN specifically, |
@christopherhein @Fei-Guo Thank you, I will try the VC demo first, before the CAPN+VC integration done. |
@christopherhein @Fei-Guo Could you please answer some questions for understanding. Thanks in advanced.
|
|
To add a little more color to #1 you could technically use this and run a set of data plane nodes w/ VMs or anything else and just use pod based control planes but you'd likely need to do some customizing as well, ie as of today that isn't supported. |
@Fei-Guo @christopherhein Thank you for your explanation ! |
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 |
/remove-lifecycle stale |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
Follow the guide:
https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/docs/README.md
The memcached pod is always pending, but the same deployment can work on real kubernetes environment
What did you expect to happen:
The memcatched pods are running, just like
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The deploy yaml for memcached
Environment:
kubectl version
): v1.21.1/etc/os-release
): Red Hat Enterprise Linux 8/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: