public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Sync content from rancher/docs

Browse Source 
Start: cb708da8d Jul 7 2022
End: 09d646cfc Sep 2 2022
This commit is contained in:
Billy Tat
2022-09-09 14:21:51 -07:00
parent 38da4eb019
commit 80b78c98d5
62 changed files with 1868 additions and 467 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/troubleshooting/other-troubleshooting-tips/expired-webhook-certificate-rotation.md
+2 -2
View File
@@ -3,9 +3,9 @@ title: Rotation of Expired Webhook Certificates
weight: 120
---
For Rancher versions that have `rancher-webhook` installed, these certificates will expire after one year. It will be necessary for you to rotate your webhook certificate when this occurs.
For Rancher versions that have `rancher-webhook` installed, certain versions created certificates that will expire after one year. It will be necessary for you to rotate your webhook certificate if the certificate did not renew.
Rancher will advise the community once there is a permanent solution in place for this known issue. Currently, there are two methods to work around this issue:
In Rancher v2.6.3 and up, rancher-webhook deployments will automatically renew their TLS certificate when it is within 30 or fewer days of its expiration date. If you are using v2.6.2 or below, there are two methods to work around this issue:
##### 1. Users with cluster access, run the following commands:
```
docs/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md
+8
View File
@@ -126,10 +126,18 @@ kubectl -n ingress-nginx describe pods -l app=ingress-nginx
### Pod container logs
The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information.
```
kubectl -n ingress-nginx logs -l app=ingress-nginx
```
If the full log is needed, specify the pod name in the trailing command:
```
kubectl -n ingress-nginx logs <pod name>
```
### Namespace events
```