keyvault-acmebot
cert-manager
keyvault-acmebot | cert-manager | |
---|---|---|
9 | 101 | |
836 | 11,486 | |
- | 1.1% | |
7.6 | 9.8 | |
8 days ago | 4 days ago | |
C# | 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.
keyvault-acmebot
- How do you keep track / manage your SSL certificates?
-
Need Help Understanding Ingress Controller TLS (AKS)
I used the following stack to generate and sync my certificate : Generation of certs to Keyvault : https://github.com/shibayan/keyvault-acmebot Keyvault cert to AKS sync : https://akv2k8s.io/
-
gRPC + Reverse Proxy
So far I've been able to set up Keyvault Acmebot, and that seems to be working very well, but the piece that's eluding me is a functional gRPC reverse proxy. Is there a set of tools in Azure that can handle this?
-
How do you request and manage certificates on the application gateway level?
I’ve used https://github.com/shibayan/keyvault-acmebot before and loved it if you can stand the occasional click ops.
-
Nginx Proxy Manager in Azure (as MS service)?
App Gateway does have manual certs, yes, but it can do redirection (HTTP 30x). I've used it personally with keyvault-acmebot to handle Let's Encrypt certificates and renewals.
-
Wildcard SSL for inward-only facing, non-critical, non -PHI, non-confidential systems?
If you happen to be using things in Azure already (or are okay with adding a few), I've found this solution to be very useful https://github.com/shibayan/keyvault-acmebot as it just drops the certificates in Azure KeyVault and keeps them updated.
-
Azure equivalent of Amazon's ACM?
I use this in production at my job and love it: https://github.com/shibayan/keyvault-acmebot
- Web cert questions
-
Azure Key Vault Certificates with Let’s Encrypt as the Issuer CA
Really you should automate this process. I suggest keyvault-acmebot https://github.com/shibayan/keyvault-acmebot
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?
Posh-ACME - PowerShell module and ACME client to create certificates from Let's Encrypt (or other ACME CA)
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
win-acme - A simple ACME client for Windows (for use with Let's Encrypt et al.)
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
certify - Professional ACME Client for Windows. Certificate Management UI, powered by Let's Encrypt and compatible with all ACME v2 CAs. Download from certifytheweb.com
Portainer - Making Docker and Kubernetes management easy.
app-service-announcements - Subscribe to this repo to be notified about major changes in App Service
awx-operator - An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
letsencrypt-siteextension - Azure Web App Site Extension for easy installation and configuration of Let's Encrypt issued SSL certifcates for custom domain names.
k3s - Lightweight Kubernetes
OnDotNetConfiguration - A sample ASP.NET Core 5.0 Blazor Server app to accompany the On .NET episodes
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.