cluster-api-provider-azure
cluster-api-provider-nested
| cluster-api-provider-azure | cluster-api-provider-nested | |
|---|---|---|
| 4 | 6 | |
| 285 | 293 | |
| 0.4% | -0.3% | |
| 9.8 | 4.7 | |
| 6 days ago | 13 days ago | |
| Go | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cluster-api-provider-azure
- Anyway to automate the AKS cluster creation using Yaml?
-
Kubernetes CRD/Operators for Azure resources
Azure already has something similar (https://github.com/Azure/azure-service-operator) and they recommend it over something like Crossplane. I do not have experience with it however. We use https://cluster-api.sigs.k8s.io/ & https://github.com/kubernetes-sigs/cluster-api-provider-azure for AKS, and Crossplane for PostgreSQL & blob storage.
-
Is it possible to upgrade a node's kubelet using an operator?
We use https://cluster-api.sigs.k8s.io/ & https://github.com/kubernetes-sigs/cluster-api-provider-azure on production for AKS clusters. We do something similar for GKE clusters but we have our custom operator for that.
- Kubernetes-in-Kubernetes and the WEDOS PXE bootable server farm
cluster-api-provider-nested
-
Amazon EC2 Enhances Defense in Depth with Default IMDSv2
Kubernetes has a lot of limitations from a multi tenancy perspective.
It's functional, but I think it's not as polished as the rest of Kubernetes which is why Kubernetes has a multi tenancy SIG that spawned the hierarchical namespace controller (https://github.com/kubernetes-sigs/hierarchical-namespaces) and virtual clusters (https://github.com/kubernetes-sigs/cluster-api-provider-nest...)
-
Multi-tenancy in Kubernetes
Virtual Cluster (wg-multitenancy)
-
Any projects to run Kubernetes inside Kubernetes?
Also https://github.com/kubernetes-sigs/cluster-api-provider-nested, similar approach to vcluster, but part of the K8s project.
- cluster-api-provider-nested/virtualcluster at main ยท kubernetes-sigs/cluster-api-provider-nested
- Kubernetes-in-Kubernetes and the WEDOS PXE bootable server farm
-
Introduction to Multi-Tenancy in Kubernetes
Approach C This approach provides a way to implement hard isolation among Kubernetes tenants who have no trust between them. This provides segregated master plane components for each tenant by creating a mini virtual cluster on the super Kubernetes cluster. Admins can also create custom resources in those virtual clusters as well. This is provided by projects like VirtualCluster and vCluster.
What are some alternatives?
cluster-api-provider-openstack
vcluster - vCluster - Create fully functional virtual Kubernetes clusters - Each vcluster runs inside a namespace of the underlying k8s cluster. It's cheaper than creating separate full-blown clusters and it offers better multi-tenancy and isolation than regular namespaces.
cluster-api-provider-kubevirt - Cluster API Provider for KubeVirt
provider-jet-azure
kamaji - Kamaji is the Hosted Control Plane Manager for Kubernetes.
cluster-api-provider-vsphere
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
cluster-api-provider-packet - Cluster API Provider Packet (now Equinix Metal)