vcluster Scheduler
vcluster now supports running a scheduler inside the virtual cluster. This is especially useful if you need to label and taint nodes within the vcluster and do not want to label or taint the actual host nodes. The scheduler can be enabled via:
sync:
nodes:
enabled: true
syncAllNodes: true # or use nodeSelector
enableScheduler: true
This will tell vcluster to now start the scheduler inside vcluster and will only sync pods that have a node assigned.
Changes
- syncer: Use the vcluster service label selector for creating a fake kubelet service instead of finding out the pod label selector
- syncer: vcluster will now sync service selectors by default for better compatibility and reduced permission surface of vcluster instead of syncing all endpoints. vcluster will still sync endpoints for services that have no selector
- syncer: Fixed an issue where vcluster would not sync the increased persistent volume size back to the virtual cluster
- syncer: Fixed an issue where vcluster wouldn't sync ClusterIP to LoadBalancer change correctly
- syncer: vcluster will now recreate a PVC inside the virtual cluster if there is a corresponding host PVC with a different volume name
- syncer: Fixed an issue where
default/kubernetesEndpoints object was referencing incorrect IPs in k8s and eks flavors. - syncer: vcluster will now try to reapply the kube config secret periodically
- syncer: Fixed an issue where vcluster would try to bind a virtual pod multiple times to a node
- syncer: Use the vcluster service label selector for creating a fake kubelet service instead of finding out the pod label selector
- syncer: Update vcluster default go runtime to 1.18
- chart: Add
isolation.namespace - chart: Enable CoreDNS multi-replica deployments via .coredns.replicas helm value
- chart: Add RFC6598 address space to network policy (thanks @desponda)