-
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
🐛 Unable to create a VirtualCluster on k8 v1.20.2 #63
Comments
I think the ClusterVersion crd schema introduces the problem. It is not a good idea to put StatefulSet schema directly in CRD Spec, we should define Pod spec instead. To quickly workaround the problem, please change the ClusterVersion CRD schema to a much simpler version shown as below. I hope this can unblock you at least for now.
|
Another attempt is to remove your controller-gen, the make script will download controller-gen0.3.0 which seems to be working fine previously. You can check the make file to see more tricks for manipulating the crd, e.g:
|
Same result with controller-gen 0.3.0. I think the x-kubernetes-list-map-keys were added in 0.3.0 but at this time there was no validation in place. However, your workaround fixed the issue. Here is my first virtual cluster:
Is there a way to enforce a specific runtimeClassName for pods with the syncer? This woudl be great to enforce tolerations and a container runtime like kata for pods running on the super cluster. |
Forgot a |
If vPod specifies runtimeClassName to Kata, it should work. If you want to enforce/overwrite vPod runtimeClassTime to be fixed to Kata, you need to change the syncer code. |
/retitle 🐛 Unable to create a VirtualCluster on k8 v1.20.2 |
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 |
We have another issue creating VirtualCluster in 1.20, where we have apiserver v1.19:
It is fixed in kubernetes/kubernetes#95423 and I will test conversion of fields to pointers shortly, to be compatible with 1.19 too fluid-cloudnative/fluid#1551 (comment) |
Problem
Virtual cluster does not deploy with k8 v1.20.2. Output from vc-manager:
The namespace and secrets were created but none of the statefulsets from the ClusterVersion.
What I did
Build kubectl-vc
Create new CRDs
(see #62)
Install CRD
Create ns, rbac, deployment, ...
I've added
events
to the RBAC because of this:Create a new ClusterVersion
Had to remove kind and apiVersion below controllerManager: to match the schema:
Create a new VirtualCluster
The text was updated successfully, but these errors were encountered: