Table of contents generated with markdown-toc
This project is here to make it easier to run common services in kubernetes by taking care of it for you so that you can get to working on your application faster instead of dealing with infrastructure components.
When running your application in Kubernetes, you often add various open source applications to your cluster to help you automatically get Let's Encrypt certificates for your HTTPS endpoints and automatically renewing them, automatically sync DNS entries that you have on an ingress to your DNS provider, monitoring and alerting for your cluster, and many more items.
These services are super fantastic and works really well but it takes time to set them up, integrate it into your cluster and then over the lifetime of it, you have to revisit each one to update them. This is all undifferentiated heavy lifting that you have to take care of in addition to your own application.
This project integrates and maintains (with updates) all of these open source applications for you so you don't have to do it.
This project is for people who do not want to manage these common applications and let the open source community manage it. Just like how you don't manage the various pieces to Kubernetes and integrate it together, you instead use a product like GKE, EKS, AKS, Rancher, Kops, Kubespray, etc. You don't also have to manage these common Kubernetes services either. If you want to offload that work, this project is for you.
Setting up and maintaining these application and integrating it with your cloud is a lot of work you have to do before you even start on your application. This project helps accelerate your process and gets you to running your application on Kubernetes faster by taking care of the undifferentiated heavy lifting of the infrastructure work for you and keeping it maintained going forward.
There is no magic here. Everything in here you can do and everything we use is absolutely 100% open source. The value add this project provides is an opinionated way of deploying these items and the curration of each service. We put in the work to make sure everything is structured correctly, updated in a timely manor, and reasonably easy to use. The other major piece is that we validate that these pieces are working in various types of Kubernetes clusters and clouds.
- cert-manager (For HTTPS certs)
- cluster-turndown (Automated turndown of Kubernetes clusters on specific schedules.)
- external-dns (manages your DNS automatically via annotations)
- kube-metric-adapter (Scale by any Prometheus metrics)
- nginx-ingress (To expose HTTP services to consumers from outside of the cluster such as the internet)
- prometheus-blockbox-exporter (checks on URLs)
- prometheus-operator (Monitoring and alerting for your cluster)
- sealed-secrets (Keep your secrets encrypted in Git and delivered as secrets into Kubernetes)
If you don't see a service that you want to use but want us to support it, please open an issue in this project and let us know!
No, you can pick and choose which one you want to use.
We are leveraging Weaveworks Flux to provide us with the GitOps workflow.
To use these items, you need to copy the folder <repo root>/kubernetes to the root of your repository. It has to be at the root of your repository because all of the paths are pointing from that fixed location. You can change the location but then you will have to change various paths in the deployment files to point to the correct location.
You don't need to enable everything. Only copy the services that you want to deploy out.
There are detailed instructions on how to do this here.
There are detailed instructions on how to do this here.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent