cluster-api-provider-azure
cluster-api-provider-azure | cluster-version-operator | |
---|---|---|
4 | 3 | |
286 | 78 | |
0.7% | - | |
9.8 | 8.6 | |
2 days ago | 5 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-version-operator
-
New TSE in search of advice!
Try searching Bugzilla "confusing error" site:bugzilla.redhat.com and Github? Some of the information on each of the git repos are super informative. Examples: https://github.com/openshift/ https://github.com/openshift/cluster-version-operator/tree/master/docs/user https://github.com/openshift/enhancements/blob/master/dev-guide/cluster-version-operator/user/update-workflow.md
-
Is it possible to upgrade a node's kubelet using an operator?
Openshift uses https://github.com/openshift/cluster-version-operator
-
Just wrote about the differences between OpenShift and Kubernetes. Tell me what you think?
A really big point that you missed is that OpenShift uses Operators to manage the lifecycle of the cluster. The Operators manage adding and removing nodes, upgrades and updates, and generally keeping things running: https://docs.okd.io/latest/operators/understanding/olm-what-operators-are.html https://cloud.redhat.com/blog/helm-and-operators-on-openshift-part-2 https://docs.okd.io/latest/operators/operator-reference.html https://github.com/openshift/cluster-version-operator
What are some alternatives?
cluster-api-provider-openstack
system-upgrade-controller - In your Kubernetes, upgrading your nodes
cluster-api-provider-kubevirt - Cluster API Provider for KubeVirt
provider-jet-azure
cluster-api-provider-vsphere
cluster-api-provider-nested - Cluster API Provider for Nested Clusters
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
cluster-api-provider-packet - Cluster API Provider Packet (now Equinix Metal)
cluster-api-provider-metal3 - MetalĀ³ integration with https://github.com/kubernetes-sigs/cluster-api
azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl
cluster-api-provider-aws - Kubernetes Cluster API Provider AWS provides consistent deployment and day 2 operations of "self-managed" and EKS Kubernetes clusters on AWS.
eksctl - The official CLI for Amazon EKS