If you would like to use the new Make flow (we dropped Bazel!), here is a tutorial on how test cert-manager on a non-kind cluster such as GKE or OpenShift. In this tutorial, I assume that you have cloned cert-manager/cert-manager and that you have a shell session open in that folder. I also assume that your GKE or OpenShift cluster has access to the Docker Hub registry (i.e., you cluster has access to the internet).

You will need docker, helm, and crane installed. If you are on macOS or on Linux, you can install helm and crane using Homebrew:

This gist can be shared, no problem.

Update 6 June 2022: it seems like dev assistant, which was published as a Chrome extension, has been withdrawn (probably by their authors). The source code for the extension is on GitHub: https://github.com/shridhar-tl/dev-assist. I don't know how to add the extension "manually" using the source code.

In the Stackover question 70897574, user1563721 suggests that cert-manager's ACME solver is not behaving as it should with non-let's encrypt servers. More specifically, that new-order is called using kid instead of jwk. In the remainder of this page, I detail how to reproduce this issue using Pebble (a smaller version of Boulder, which is the ACME server Let's Encrypt uses).

Related:

• Erratic No Key ID in JWS header

Install cert-manager but turn off the deployment:

👉 This tutorial is also visible in the Cilium Service Mesh official documentation here.

With this tutorial, you will install Cilium Service Mesh on Kind with TLS with certificates created by cert-manager. It is inspired by the TLS example on the Cilium website.

This was written on 18 Feb 2022 during the beta of the Cilium Service Mesh. A lot probably changed since then.

Prerequisites:

• helm v3.7 and above,

We want to use Kubernetes 1.20 or lower since we need both the v1 and v1beta1 of the Ingress resource.

• ingress-gce
  • v1beta1 Ingress with just annotation
  • v1 Ingress with spec.IngressClassName but no IngressClass object
  • v1 Ingress with spec.ingressClassName and IngressClass object
• v1 Ingress with just annotation and no IngressClass object

Users will start seeing errors whenever a client tries to apply or create a v1alpha2 resource:

TODO paste the error here

https://grafana.com/orgs/maelvls/api-keys

 kubectl create secret generic kubepromsecret \
  --from-literal=username=maelvls\
  --from-literal=password= \

This gist was published at https://www.jetstack.io/blog/cert-manager-gateway-api-traefik-guide/

Contents:

• Getting started
  • Prerequisites
  • Getting started with Traefik
• Known bugs in implementations

https://kubernetes.slack.com/archives/C4NV3DWUC/p1618579222346800 https://kubernetes.slack.com/archives/C4NV3DWUC/p1612299155160000

kubectl get validatingwebhookconfigurations cert-manager-webhook -ojsonpath='{.webhooks[0].clientConfig.caBundle}' | base64 -d | openssl x509 -noout -text