Skip to content

Commit c6d5968

Browse files
violukekolchfa-aws
andauthored
Correct kubectl commands (#11492)
* Correct kubectl commands Signed-off-by: Luke Cousins <[email protected]> * Apply suggestions from code review Signed-off-by: kolchfa-aws <[email protected]> * Update _install-and-configure/install-opensearch/operator.md Signed-off-by: kolchfa-aws <[email protected]> --------- Signed-off-by: Luke Cousins <[email protected]> Signed-off-by: kolchfa-aws <[email protected]> Co-authored-by: kolchfa-aws <[email protected]>
1 parent a08470d commit c6d5968

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_install-and-configure/install-opensearch/operator.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,9 +123,9 @@ kubectl get crds | grep opensearch
123123
```
124124
{% include copy.html %}
125125

126-
If you deployed the operator using [Helm charts](#use-a-helm-chart), to ensure that Kubernetes recognizes the OpenSearch Kubernetes Operator as a namespace, enter `k get ns | grep opensearch`. Both `opensearch` and `opensearch-operator-system` should appear as `Active`.
126+
If you deployed the operator using [Helm charts](#use-a-helm-chart), verify that Kubernetes recognizes the OpenSearch Kubernetes Operator namespaces by running `kubectl get ns | grep opensearch`. Both `opensearch` and `opensearch-operator-system` should appear as `Active`.
127127

128-
With the operator active, use `k get pod -n opensearch-operator-system` to make sure that the operator's pods are running.
128+
With the operator active, verify that the operator's pods are running by executing `kubectl get pod -n opensearch-operator-system`. All pods should have the `Running` status.
129129

130130
```
131131
NAME READY STATUS RESTARTS AGE

0 commit comments

Comments
 (0)