Minor documentation cleanup (#7826)
* clarify link * Add section headers * console blocks * grpc example json was not valid * multi-tls update text The preceding point 1 related to4f2cb51ef8/ingress/controllers/nginx/examples/ingress.yamland the deployments referenced in4f2cb51ef8/ingress/controllers/nginx/examples/README.mdThey are not relevant to the current instructions. * add whitespace around parens * grammar setup would be a proper noun, but it is not the intended concept, which is a state * grammar * is-only * via * Use bullets for choices * ingress-controller nginx is a distinct brand. generally this repo talks about ingress-controller, although it is quite inconsistent about how... * drop stray paren * OAuth is a brand and needs an article here also GitHub is a brand * Indent text under numbered lists * use e.g. * Document that customer header config maps changes do not trigger updates This should be removed if https://github.com/kubernetes/ingress-nginx/issues/5238 is fixed. * article * period * infinitive verb + period * clarify that the gRPC server is responsible for listening for TCP traffic and not some other part of the backend application * avoid using ; and reword * whitespace * brand: gRPC * only-does is the right form `for` adds nothing here * spelling: GitHub * punctuation `;` is generally not the right punctuation... * drop stray `to` * sentence * backticks * fix link * Improve readability of compare/vs * Renumber list * punctuation * Favor Ingress-NGINX and Ingress NGINX * Simplify custom header restart text * Undo typo damage Co-authored-by: Josh Soref <jsoref@users.noreply.github.com>
This commit is contained in:
parent
784f9c53bb
commit
1614027cd4
27 changed files with 208 additions and 169 deletions
|
|
@ -226,7 +226,9 @@ Use the `--service <service>` flag if your `ingress-nginx` `LoadBalancer` servic
|
|||
|
||||
### ingresses
|
||||
|
||||
`kubectl ingress-nginx ingresses`, alternately `kubectl ingress-nginx ing`, shows a more detailed view of the ingress definitions in a namespace. Compare:
|
||||
`kubectl ingress-nginx ingresses`, alternately `kubectl ingress-nginx ing`, shows a more detailed view of the ingress definitions in a namespace.
|
||||
|
||||
Compare:
|
||||
|
||||
```console
|
||||
$ kubectl get ingresses --all-namespaces
|
||||
|
|
@ -235,7 +237,7 @@ default example-ingress1 testaddr.local,testaddr2.local localhost 80
|
|||
default test-ingress-2 * localhost 80 5d
|
||||
```
|
||||
|
||||
vs
|
||||
vs.
|
||||
|
||||
```console
|
||||
$ kubectl ingress-nginx ingresses --all-namespaces
|
||||
|
|
@ -272,7 +274,7 @@ Checking deployments...
|
|||
https://github.com/kubernetes/ingress-nginx/issues/3808
|
||||
```
|
||||
|
||||
to show the lints added **only** for a particular `ingress-nginx` release, use the `--from-version` and `--to-version` flags:
|
||||
To show the lints added **only** for a particular `ingress-nginx` release, use the `--from-version` and `--to-version` flags:
|
||||
|
||||
```console
|
||||
$ kubectl ingress-nginx lint --all-namespaces --verbose --from-version 0.24.0 --to-version 0.24.0
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue