Open jinsongo opened 3 years ago
@Fei-Guo @christopherhein @charleszheng44 @gyliu513
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, https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/virtualcluster/doc/demo.md
@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.
1) Yes 2) CAPN is the replacement for the original ClusterVersion CR/controller in VC. It follows CAPI standard and has much better manageability for tenant control plane Pods.
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale /lifecycle frozen
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]