cert-manager
awx-operator
Our great sponsors
cert-manager | awx-operator | |
---|---|---|
101 | 46 | |
11,457 | 1,135 | |
1.5% | 3.0% | |
9.8 | 9.2 | |
about 6 hours ago | 7 days ago | |
Go | Jinja | |
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.
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
awx-operator
-
The Bullhorn #114 (Ansible Newsletter)
We're happy to announce that AWX Version 23.0.0 is now available! We're happy to announce that AWX Operator version 2.5.2 is now available!
-
CrashLoopBackOff on awx task pods
So what did I do wrong here ?! I followed the guide step by step (https://github.com/ansible/awx-operator) but still failed.
- Installing AWX on a macbook m1
-
Anyone have luck installing multiple AWX instances in the same cluster?
AH. I checked and found this open issue: https://github.com/ansible/awx-operator/issues/1391
-
The Bullhorn #103 (Ansible Newsletter)
Please see the releases pages for more details: AWX, Operator.
-
Ansible but with a GUI
awx has an operator - https://github.com/ansible/awx-operator
-
how to configure plays in AWX tower after installing it on k8s.
I'm now attempting a POC to use k8s, despite having limited experience with it. I've successfully deployed AWX using the https://github.com/ansible/awx-operator on k8s, which includes Postgres. However, I'm unsure how to configure AWX with the plays that we publish in our CI/CD pipeline.
-
Ansible Automation Platform - Container Orchestration?
You can look at the operator source code https://github.com/ansible/awx-operator to see exactly what it does.
-
Upgrade ansible version in awx-operator in community.vmware
I have setup AWX Operator from https://github.com/ansible/awx-operator and everything works ok. But there's an annoying warning when running modules from the community.vmware collection.
-
The Bullhorn #86 (Ansible Newsletter)
We're happy to announce that AWX version 21.10.2 is now available! We're happy to announce that AWX Operator version 1.1.3 is now available! This AWX version downgrades a dependency which was causing tracebacks to appear often in the logs of some deployments.
What are some alternatives?
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
awx - AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
awx-on-k3s - An example implementation of AWX on single node K3s using AWX Operator, with easy-to-use simplified configuration with ownership of data and passwords.
Portainer - Making Docker and Kubernetes management easy.
awx-ee - An Ansible execution environment for AWX project
k3s - Lightweight Kubernetes
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
semaphore - Modern UI for Ansible