Universal-Kubernetes-Helm-Charts
eksctl
Our great sponsors
Universal-Kubernetes-Helm-Charts | eksctl | |
---|---|---|
17 | 59 | |
101 | 4,781 | |
- | 1.2% | |
6.7 | 9.5 | |
20 days ago | 3 days ago | |
Smarty | Go | |
MIT License | GNU General Public License v3.0 or later |
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.
Universal-Kubernetes-Helm-Charts
-
Dedpulication standards of Helm Charts values file for a global chart with subcharts for our app. What's the right way to only need to specify a value once?
I would point you to what I call the "Universal Helm Charts" and some examples of how to use them.
-
Monitoring many cluster k8s
Shameless Plug: Here's one of my dashboards I made for Ingress-Nginx, which is my recommended border router/gateway into all the services. It adds deep robust metrics and configurability, and if you've got years of experience with Nginx also, it allows you rich complex customization via nginx's configuration structure via kubernetes annotations. Besides that I have open-source helm charts which are easy to use, boilerplates showing how to use them, a volume autoscaler to automatically resize your disks as they get full, and a blog where I share various of my experience which is a companion blog to my upcoming book of the same name. Hope this helps! Feel free to ask if you have any further questions.
-
Best way of managing Helm?
You may want to check out some other of my Helm Boilerplates to explain and highlight how using subcharts works. This is a companion repo to my upcoming DevOps + Kubernetes book. You also might like to check out my set of open-source universal helm charts which are published in a helm registry right now that you can leverage and has many industry best-practices built into it, such as anti-affinity rules, pod disruption budgets, horizontal pod autoscaling, ingress, service support, etc.
-
How do you guys on Mac M1's get around the annoying port forwarding issues with k8s + docker?
References: I use docker and Kubernetes daily. I currently manage numerous clusters and maintain pipelines for hundreds of microservices as I type this. I've been converting microservices into Docker images for companies hundreds if not thousands of times by now over the last bunches of years. I am also an avid and passionate open-source evangelist and Kubernetes/DevOps consultant. I author some Kubernetes controllers such as the Volume Autoscaler and have a set of Open Source Helm Charts and I love to contribute code/fixes wherever I run into issues.
-
StatelessSet Resource Type ?
If it helps at all I have some universal helm charts that have a template for easily deploying your application as a deployment or statefulset. You will notice I don’t even have a daemonset chart because it doesn’t make sense to. https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts
-
Helm makes it overly complex, or is it just me?
See: Open-Source Universal Helm Charts See: Boilerplates of using Open-Source Helm Charts (as a sub-chart)
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
Helm charts - https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts Example using helm charts as sub charts - https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver
- How do you guys manage your deployment pipelines?
-
Monthly 'Shameless Self Promotion' thread - 2023/01
A open-source set of Universal Helm Charts with tons of best-practices baked into it such as autoscaling, PDBs, labeling, and an standardized set of "universal" templates that allows you to pivot between templates easily (meaning, you can easily make a deployment into a Statefulset or a Cronjob). Yes, I need to add more documentation, I know. I'm busy :P
-
Creating Kubernetes Templates
Universal Kubernetes Helm Charts
eksctl
-
Auto-scaling DynamoDB Streams applications on Kubernetes
There are a variety of ways in which you can create an Amazon EKS cluster. I prefer using eksctl CLI because of the convenience it offers. Creating an an EKS cluster using eksctl, can be as easy as this:
-
How to migrate Apache Solr from the existing cluster to Amazon EKS
There are many ways to create a cluster such as using eksctl. In my case, I will use terraform module cause it’s easy to reuse and comprehend.
-
Ultimate EKS Baseline Cluster: Part 1 - Provision EKS
eksctl [eksctl] is the tool that can provision EKS cluster as well as supporting VPC network infrastructure.
-
[AWS] EKS vs Self managed HA k3s running on 1x2 ec2 machines, for medium production workload
For this and many other reasons I recommend doing everything in Terraform EXCEPT EKS and its node groups. For that, I use https://eksctl.io/ because it much better manages the lifecycle of EKS and your node groups. I have an blog article better explaining why I recommend it, and another blog article explaining how to do zero-downtime upgrades with EKSCTL.
-
Automating Kong API Gateway deployment with Flux
eksctl
- Export a docker container to a VPC in AWS and exposing it publicly through a loadbalancer
-
Anybody using spot instances for worker nodes?
Second, make sure you create a spot instance group that attempts to launch MULTIPLE different instance types. This way if one instance type gets flushed, your autoscaler will kick in and launch a different type. Without this, you WILL HAVE DOWNTIME if a sudden price hike and flush occurs. If you're using eksctl I have example configurations that use multi-instance types on Github here.
-
Use AWS Controllers for Kubernetes to deploy a Serverless data processing solution with SQS, Lambda and DynamoDB
There are a variety of ways in which you can create an Amazon EKS cluster. I prefer using eksctl CLI because of the convenience it offers. Creating an an EKS cluster using eksctl, can be as easy as this:
-
strategy to upgrade eks cluster
I've written an article on this, with my recommended tool for managing eks EKSCTL.
-
Bootstrapping Kubernetes Cluster with CloudFormation
--- AWSTemplateFormatVersion: '2010-09-09' Parameters: VpcId: Type: AWS::EC2::VPC::Id Description: ID of the VPC in which to create the Kubernetes cluster SubnetIds: Type: List Description: List of Subnet IDs in which to create the Kubernetes cluster KeyPairName: Type: AWS::EC2::KeyPair::KeyName Description: Name of the EC2 Key Pair to use for SSH access to worker nodes ClusterName: Type: String Description: Name of the Kubernetes cluster to create Resources: ControlPlaneSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: VpcId: !Ref VpcId GroupDescription: Allow inbound traffic to the Kubernetes control plane SecurityGroupIngress: - IpProtocol: tcp FromPort: 22 ToPort: 22 CidrIp: 0.0.0.0/0 WorkerNodeSecurityGroup: Type: AWS::EC2::SecurityGroup Properties: VpcId: !Ref VpcId GroupDescription: Allow inbound traffic to Kubernetes worker nodes SecurityGroupIngress: - IpProtocol: tcp FromPort: 22 ToPort: 22 CidrIp: 0.0.0.0/0 ControlPlaneInstanceProfile: Type: AWS::IAM::InstanceProfile Properties: Roles: - !Ref ControlPlaneRole ControlPlaneRole: Type: AWS::IAM::Role Properties: AssumeRolePolicyDocument: Version: '2012-10-17' Statement: - Effect: Allow Principal: Service: - ec2.amazonaws.com Action: - sts:AssumeRole ManagedPolicyArns: - arn:aws:iam::aws:policy/AmazonEKSClusterPolicy - arn:aws:iam::aws:policy/AmazonEKSServicePolicy ControlPlaneInstance: Type: AWS::EC2::Instance Properties: ImageId: ami-0b69ea66ff7391e80 InstanceType: t2.micro KeyName: !Ref KeyPairName NetworkInterfaces: - DeviceIndex: 0 AssociatePublicIpAddress: true GroupSet: - !Ref ControlPlaneSecurityGroup SubnetId: !Select [0, !Ref SubnetIds] IamInstanceProfile: !Ref ControlPlaneInstanceProfile UserData: Fn::Base64: !Sub | #!/bin/bash echo 'net.bridge.bridge-nf-call-iptables=1' | tee -a /etc/sysctl.conf sysctl -p yum update -y amazon-linux-extras install docker -y service docker start usermod -a -G docker ec2-user curl -o /usr/local/bin/kubectl https://amazon-eks.s3.us-west-2.amazonaws.com/1.21.2/2021-07-05/bin/linux/amd64/kubectl chmod +x /usr/local/bin/kubectl echo 'export PATH=$PATH:/usr/local/bin' >> /etc/bashrc curl --silent --location "https://github.com/weaveworks/eksctl/releases
What are some alternatives?
Helm-Chart-Boilerplates - Example implementations of the universal helm charts
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
charts - TrueNAS SCALE Apps Catalogs & Charts
kops - Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
argo-cd - Declarative Continuous Deployment for Kubernetes
helm-promotion-sample-app - Sample application that is promoted from QA to Staging to Production
terraform-aws-eks-blueprints - Configure and deploy complete EKS clusters.
Chalice-PynamoDB-Docker-Starter-Kit - A starter kit with some boilerplate code for getting started making low-cost serverless applications in Python on AWS with a great local development setup via Docker Compose
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
sparrowci_web - ci.sparrowhub.io website
eks-anywhere - Run Amazon EKS on your own infrastructure 🚀