Skip to content

Commit a664d53

Browse files
salonichf5sjberman
andauthored
Update site/content/how-to/monitoring/troubleshooting.md
Co-authored-by: Saylor Berman <[email protected]>
1 parent 3f076de commit a664d53

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/content/how-to/monitoring/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ To view the access logs, get shell access to your NGINX container using the [ste
123123

124124
You can see logs for a crashed or killed container by adding the `-p` flag to the above commands.
125125

126-
##### If NGINX Gateway Fabric Pod is not running or ready
126+
##### NGINX Gateway Fabric Pod is not running or ready
127127

128128
To understand why NGINX Gateway Fabric Pod has not started running or is not ready, first step is to check the state of the pod to get a detailed information about the current status and events happening in the pod. To do this, use `kubectl describe`:
129129

0 commit comments

Comments
 (0)