deckhouse
cert-manager
deckhouse | cert-manager | |
---|---|---|
9 | 101 | |
1,010 | 11,486 | |
1.6% | 1.1% | |
9.9 | 9.8 | |
2 days ago | 1 day ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
deckhouse
-
K3s – Lightweight Kubernetes
And while k3s sounds easy, it's not after even a slightly larger scale.
If one willing to have in-house k8s today I would recommend https://deckhouse.io/ (I'm not affiliated with them)
-
What's your preferred tool for on-premise k8s installer?
Deckhouse
-
Self-Managed Kubernetes Distributions
Check Deckhouse as well (https://github.com/deckhouse/deckhouse). Cilium integration was added there recently.
-
FOSS News International #3: November 15-21, 2021
Release Deckhouse v1.26.0 · deckhouse/deckhouse (github.com)
-
Which on-prem distribution to use?
Consider Deckhouse as another option that can be installed everywhere: bare metal, private and public clouds. It has an Open Source core offered in Community Edition, but the pricing for Enterprise Edition is also a fit for small companies. All configuration is made via Custom Resources, all routines (like updating Kubernetes versions and related system components) are automated.
-
Does anybody need a Kubernetes Operator for auto renewing SSL certificates?
We use cert-manager in our K8s platform for years and it works perfectly. I don't think there is any chance today to compete with it in terms of community adoption. I also can't find any GitHub links for your project which is the most widely accepted way to become trusted by the community — simply because it covers all the basic needs everyone got used to (in the Open Source world): we can see how the code is developed, we can contribute to it, discuss the issues and concerns we have, etc.
-
Log shipper for Loki
We use Vector to ship logs to different storages (including Loki). You can even find the implementation here, however, I am not sure how useful it might be since it's quite specific (Golang hooks for addon-operator). Our manifests are available there as well.
- Deckhouse is a platform for managing Kubernetes clusters in a fully automatic and uniform fashion. It allows you to create homogeneous Kubernetes clusters anywhere and fully manages them. It supplies all necessary addons to provide observability, security, and service mesh.
- Deckhouse: NoOps Kubernetes platform
cert-manager
-
deploying a minio service to kubernetes
cert-manager
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
Run WebAssembly on DigitalOcean Kubernetes with SpinKube - In 4 Easy Steps
On top of its core components, SpinKube depends on cert-manager. cert-Manager is responsible for provisioning and managing TLS certificates that are used by the admission webhook system of the Spin Operator. Let’s install cert-manager and KWasm using the commands shown here:
-
Importing kubernetes manifests with terraform for cert-manager
terraform { required_providers { kubectl = { source = "gavinbunney/kubectl" version = "1.14.0" } } } # The reference to the current project or a AWS project data "google_client_config" "provider" {} # The reference to the current cluster or EKS data "google_container_cluster" "my_cluster" { name = var.cluster_name location = var.cluster_location } # We configure the kubectl provider to use those values for authenticating provider "kubectl" { host = data.google_container_cluster.my_cluster.endpoint token = data.google_client_config.provider.access_token cluster_ca_certificate = base64decode(data.google_container_cluster.my_cluster.master_auth[0].cluster_ca_certificate) } #Download the multiple manifests file. data "http" "cert_manager_crds" { url = "https://github.com/cert-manager/cert-manager/releases/download/v${var.cert_manager_version}/cert-manager.crds.yaml" } data "kubectl_file_documents" "cert_manager_crds" { content = data.http.cert_manager_crds.response_body lifecycle { precondition { condition = 200 == data.http.cert_manager_crds.status_code error_message = "Status code invalid" } } } # We use the for_each or else this kubectl_manifest will only import the first manifest in the file. resource "kubectl_manifest" "cert_manager_crds" { for_each = data.kubectl_file_documents.cert_manager_crds.manifests yaml_body = each.value }
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
SSL certificates thanks to Cloudflare and cert-manager
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml
-
Setup/Design internal PKI
put the Sub-CA inside hashicorp vault to be used for automatic signing of services like https://cert-manager.io/ inside our k8s clusters.
-
Task vs Make - Final Thoughts
install-cert-manager: desc: Install cert-manager deps: - init-cluster cmds: - kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/{{.CERT_MANAGER_VERSION}}/cert-manager.yaml - echo "Waiting for cert-manager to be ready" && sleep 25 status: - kubectl -n cert-manager get pods | grep Running | wc -l | grep -q 3
-
Easy HTTPS for your private networks
I've been pretty frustrated with how private CAs are supported. Your private root CA can be maliciously used to MITM every domain on the Internet, even though you intend to use it for only a couple domain names. Most people forget to set Name Constraints when they create these and many helper tools lack support [1][2]. Worse, browser support for Name Constraints has been slow [3] and support isn't well tracked [4]. Public CAs give you certificate transparency and you can subscribe to events to detect mis-issuance. Some hosted private CAs like AWS's offer logs [5], but DIY setups don't.
Even still, there are a lot of folks happily using private CAs, they aren't the target audience for this initial release.
[1] https://github.com/FiloSottile/mkcert/issues/302
[2] https://github.com/cert-manager/cert-manager/issues/3655
[3] https://alexsci.com/blog/name-non-constraint/
[4] https://github.com/Netflix/bettertls/issues/19
[5] https://docs.aws.amazon.com/privateca/latest/userguide/secur...
-
☸️ Managed Kubernetes : Our dev is on AWS, our prod is on OVH
the Cert Manager
What are some alternatives?
kubernetes - Production-Grade Container Scheduling and Management
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
kubespray - Deploy a Production Ready Kubernetes Cluster
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
k3s-on-prem-production - Playbooks needed to set up an on-premises K3s cluster and securize it
Portainer - Making Docker and Kubernetes management easy.
minikube - Run Kubernetes locally
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
k3s - Lightweight Kubernetes
vector - A high-performance observability data pipeline.
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.