From dfd35892f21d027ce3c0792f933111f28ba16a1c Mon Sep 17 00:00:00 2001
From: rtsp <git@rtsp.us>
Date: Fri, 20 Aug 2021 08:31:24 +0700
Subject: [PATCH] docs/cert_manager.md: Update docs for K8s v1.22 (#7877)

---
 docs/cert_manager.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/cert_manager.md b/docs/cert_manager.md
index 241efc933..d70f2596c 100644
--- a/docs/cert_manager.md
+++ b/docs/cert_manager.md
@@ -56,7 +56,7 @@ ingress_nginx_enabled: true
 For example, if you're using the Nginx ingress controller, you can secure the Prometheus ingress by adding the annotation `cert-manager.io/cluster-issuer: ca-issuer` and the `spec.tls` section to the `Ingress` resource definition.
 
 ```yaml
-apiVersion: networking.k8s.io/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   name: prometheus-k8s
@@ -76,9 +76,12 @@ spec:
     http:
       paths:
       - path: /
+        pathType: ImplementationSpecific
         backend:
-          serviceName: prometheus-k8s
-          servicePort: web
+          service:
+            name: prometheus-k8s
+            port:
+              name: web
 ```
 
 Once deployed to your K8s cluster, every 3 months cert-manager will automatically rotate the Prometheus `prometheus.example.com` TLS client certificate and key, and store these as the Kubernetes `prometheus-dashboard-certs` secret.