status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-02-20 01:18:49 +00:00
Code Issues Projects Releases Wiki Activity

docs: consul-k8s service mesh overview - move verification section (#12500)

Browse Source
This commit is contained in:
David Yu 2022-03-03 08:11:28 -08:00 committed by GitHub
parent 5ba994a73f
commit c8865be799
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
website/content/docs/k8s/connect/index.mdx
View File

@ -394,6 +394,19 @@ This will configure the injector to inject when the
is set to `true`. Other values in the Helm chart can be used to limit the namespaces is set to `true`. Other values in the Helm chart can be used to limit the namespaces
the injector runs in, enable injection by default, and more. the injector runs in, enable injection by default, and more.
### Verifying the Installation
To verify the installation, run the
["Accepting Inbound Connections"](/docs/k8s/connect#accepting-inbound-connections)
example from the "Usage" section above. After running this example, run
`kubectl get pod static-server --output yaml`. In the raw YAML output, you should
see injected Connect containers and an annotation
`consul.hashicorp.com/connect-inject-status` set to `injected`. This
confirms that injection is working properly.
If you do not see this, then use `kubectl logs` against the injector pod
and note any errors.
### Controlling Injection Via Annotation ### Controlling Injection Via Annotation
By default, the injector will inject only when the By default, the injector will inject only when the
@ -545,16 +558,3 @@ See [consul.hashicorp.com/connect-service-upstreams](#consul-hashicorp-com-conne
-> **Note:** When you specify upstreams via an upstreams annotation, you will need to use -> **Note:** When you specify upstreams via an upstreams annotation, you will need to use
`localhost:<port>` with the port from the upstreams annotation instead of KubeDNS to connect to your upstream `localhost:<port>` with the port from the upstreams annotation instead of KubeDNS to connect to your upstream
application. application.
### Verifying the Installation
To verify the installation, run the
["Accepting Inbound Connections"](/docs/k8s/connect#accepting-inbound-connections)
example from the "Usage" section above. After running this example, run
`kubectl get pod static-server --output yaml`. In the raw YAML output, you should
see injected Connect containers and an annotation
`consul.hashicorp.com/connect-inject-status` set to `injected`. This
confirms that injection is working properly.
If you do not see this, then use `kubectl logs` against the injector pod
and note any errors.