acme2certifier
kubetls
acme2certifier | kubetls | |
---|---|---|
2 | 5 | |
143 | - | |
- | - | |
9.6 | - | |
3 days ago | - | |
Python | ||
GNU General Public License v3.0 only | - |
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.
acme2certifier
kubetls
-
Do I even need istio?
Hi! I wrote a thing called KubeTLS that automatically provisions MTLS certificates per-pod. It is not necessarily simpler than KubeTLS, because you need a lot of the same components, but if you're not looking for the whole set of baggage that comes with an integrated and opinionated (and in my view, often wrong) solution, I'd be happy to help you give it a try.
-
i must be the only guy that understands certificates
I'm working on KubeTLS to make Certificates a first-class concept; though I'm also pushing Kubernetes upstream to adopt the concept. Everything should run with certs, and it's all about solving problems of trust and key distribution.
-
SSL/TLS for Kubernetes svc.cluster.local
I built a tool for just that: https://gitlab.com/gauntletwizard_net/kubetls . It's out of date and half-baked - Nowhere near production ready. It might help you start as a baseline.
-
Go HTTPS Servers with TLS
I am working towards this goal, sort of: I believe that TLS should be self-configuring. I've built a spec and some tools around automatically issuing TLS certificates automatically in a well-defined place in Kubernetes clusters. You then call my init code to start up your services - Exactly like you'd call http.ListenAndServe(), you call KubeTLS.ListenAndServe(). The code is simple enough, and there's a little script you run on your development machine to create a self-signed cert locally.
https://gitlab.com/gauntletwizard_net/kubetls
-
Google’s New ‘Autopilot’ for Kubernetes
I’m the author of a tool called KubeTLS. KubeTLS creates certificates for use in MTLS between pods in your cluster. These certificates are identified as the Service Account that the pod is running as (for use in identifying to the cluster), but also as server certificates for identifying the server to other client pods. There’s no reason those two usages couldn’t be split into two certificates, but no reason for them to be - The X509 spec and client libraries do the right thing.
What are some alternatives?
django-plausible-proxy - Django application to proxy requests and send server-side events to Plausible Analytics.
nginx-service-mesh - A service mesh powered by NGINX Plus to manage container traffic in Kubernetes environments.
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
cert-manager - Automatically provision and manage TLS certificates in Kubernetes
certmagic - Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
banking-system - A Banking System Concept Created Using Django Python Web Framework and Tailwind CSS
patchman - Patchman is a Linux Patch Status Monitoring System
policy-templates - Policy Templates for Firefox
ACME-Server-ADCS - ACME (RFC 8555) Server compatible implementation, connecting to Active Directory Certificate Services (ADCS)