apply change proposed in issue 899

Signed-off-by: Tim Ramlot <42113979+inteon@users.noreply.github.com>
cert-manager · Oct 15, 2024 · 1af4560 · 1af4560
1 parent 945ab69
commit 1af4560
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/content/docs/releases/upgrading/upgrading-1.7-1.8.md b/content/docs/releases/upgrading/upgrading-1.7-1.8.md
@@ -10,8 +10,8 @@ The field `spec.privateKey.rotationPolicy` on Certificate resources is now valid
 Before upgrading to 1.8.0, you will need to check that all the Certificate YAML manifests you have stored in Git if you are using a GitOps flow (or any other "source of truth") have a correct `rotationPolicy` value. To help you find out which Certificate YAML manifests need updating, you can run the following command:
 
 ```sh
-kubectl get cert -A -ojson | jq -r \
-  '.items[] | select(.spec.privateKey.rotationPolicy | strings | . != "Always" and . != "Never") | "\(.metadata.name) in namespace \(.metadata.namespace) has rotationPolicy=\(.spec.privateKey.rotationPolicy)"'
+kubectl get cert -A -ojson | jq -r \                      
+  '.items[] | select(.spec.privateKey) | select(.spec.privateKey.rotationPolicy | . != "Always" and . != "Never") | "\(.metadata.name) in namespace \(.metadata.namespace) has rotationPolicy=\(.spec.privateKey.rotationPolicy)"'
 ```
 
 This command will show you, the name and namespace of each Certificate resource that needs to be updated in Git. For example: