ansible-role-rke2
autoscaler
ansible-role-rke2 | autoscaler | |
---|---|---|
3 | 89 | |
264 | 7,680 | |
8.7% | 1.3% | |
8.4 | 9.7 | |
10 days ago | 1 day ago | |
Jinja | Go | |
MIT License | 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.
ansible-role-rke2
-
Questions about Kubernetes
I've implemented Kubernetes in my company during the last year. It's a great technology. I love it. By now I have 10Nodes, 3 masters and ~35 Namespaces for different applications. I use RKE2 as my kubernetes engine. I've setup the whole cluster via ansible and this module: GitHub - lablabs/ansible-role-rke2: Ansible Role to install RKE2 Kubernetes. My Servers get deployed via terraform. I host everything on hetzner.
-
Single IP (kube-vip) for ingress objects, is this possible?
I deployed Kubernetes using ansible + lablabs.rke2 role, and used Kube-vip as the virtual IP provider. Now I have a Kubernetes cluster and can create a service with type=LoadBalancer without any problem. However, the IP range that I assigned for load balancing is quite limited, so I want to use ingress instead. But when creating an ingress object, their addresses are the addresses of my 2 worker nodes. Is it possible to assign a virtual IP to distribute traffic to my worker nodes instead? I heard that DNS round-robin isn't very reliable.
-
RKE or RKE2 automation
Hello, I guess you can use an Ansible RKE2 role to provision your cluster. https://github.com/lablabs/ansible-role-rke2
autoscaler
-
Upgrading Hundreds of Kubernetes Clusters
We use Cluster Autoscaler to automatically adjust the number of nodes (cluster size) based on your actual usage to ensure efficiency. Additionally, we deploy Vertical and Horizontal Pod Autoscalers to scale your applications' resources as their needs change automatically.
-
Not Everything Is Google's Fault (Just Most Things)
> * Hetzner: cheap, good service, the finest pets in the world, no cattle
You can absolutely do cattle with Hetzner. They support imaging and immutable infrastructure. They don't have a native auto scaling equivalent, but if you're using Kubernetes, they have a cluster autoscaler: https://github.com/kubernetes/autoscaler/blob/master/cluster...
-
Kubernetes(K8s) Autoscaler — a detailed look at the design and implementation of VPA
Here we take the VPA as a starting point to analyze the design and implementation principles of the VPA in Autoscaler. The source code for this article is based on Autoscaler HEAD fbe25e1.
- Scaling with Karpenter and Empty Pod(A.k.a Overprovisioning)
-
Reducing Cloud Costs on Kubernetes Dev Envs
Autoscaling over EKS can be accomplished using either the cluster-autoscaler project or Karpenter. If you want to use Spot instances, consider using Karpenter, as it has better integrations with AWS for optimizing spot pricing and availability, minimizing interruptions, and falling back to on-demand nodes if no spot instances are available.
-
☸️ Managed Kubernetes : Our dev is on AWS, our prod is on OVH
Autoscaling is already provided on OVH, but we don't use it for now. Autoscaler has to be manually installed on the AWS/EKS cluster.
-
relevant way of scaling pods
do you mean this: https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/pkg/recommender/README.md
-
Kubernetes Cluster Maintenance
Read more about this scaler in detail here!
-
Anyone running Windows nodes in your clusters?
We have a default node group of Linux hosts, but there's a secondary nodegroup of Windows hosts that is typically scaled down to 0. When a team's build runs, a pod is scheduled based on their definition. Cluster-autoscaler will check the nodeSelector and automatically spin up a node from that nodegroup if necessary.
-
How to make sure Kubernetes autoscaler not deleting the nodes which runs specific pod
I am running a Kubernetes cluster(AWS EKS one) with Autoscaler pod So that Cluster will autoscale according to the resource request within the cluster.
What are some alternatives?
ansible-role-k3s - Ansible role for installing k3s as either a standalone server or HA cluster.
karpenter-provider-aws - Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity.
k3s-on-prem-production - Playbooks needed to set up an on-premises K3s cluster and securize it
cluster-proportional-autoscaler - Kubernetes Cluster Proportional Autoscaler Container
terraform-openstack-rke2 - Deploy Kubernetes on OpenStack with RKE2
aws-ebs-csi-driver - CSI driver for Amazon EBS https://aws.amazon.com/ebs/
libvirt-k8s-provisioner - Automate your k8s installation
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
agorakube - Agorakube is a Certified Kubernetes Distribution built on top of CNCF ecosystem that provides an enterprise grade solution following best practices to manage a conformant Kubernetes cluster for on-premise and public cloud providers.
descheduler - Descheduler for Kubernetes
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
k3s-aws-terraform-cluster - Deploy an high available K3s cluster on Amazon AWS