From 3ab58138fcc5ae0dc6e5bf874e62a4f11aeae4fb Mon Sep 17 00:00:00 2001 From: Julien Mailleret Date: Wed, 19 Feb 2020 18:02:12 +0100 Subject: [PATCH] Fix typos (#21) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3f4e8dd..63bf41c 100644 --- a/README.md +++ b/README.md @@ -281,7 +281,7 @@ This sample demonstrates how to enable the proxy mode in addition to the secrets Key annotation to use is `sidecar.vault.talend.org/mode` to let `Vault Sidecar Injector` knows that proxy mode must be enabled. Optional `sidecar.vault.talend.org/proxy-port` annotation can be handy if default proxy port has to be customized. -Once enabled, your application container can directly intereact with the Vault server by sending requests to the injected Vault Agent sidecar that now also acts as a proxy handling authentication with the server. The proxy is available at `http://127.0.0.1:`. +Once enabled, your application container can directly interact with the Vault server by sending requests to the injected Vault Agent sidecar that now also acts as a proxy handling authentication with the server. The proxy is available at `http://127.0.0.1:`. ```yaml apiVersion: v1 @@ -783,7 +783,7 @@ $ kubectl get namespace -L vault-injection #### Restrict injection to specific namespaces -By default `Vault Sidecar Injector` monitors all namespaces (except `kube-system` and `kube-public`) and looks afer annotations in submitted pods. +By default `Vault Sidecar Injector` monitors all namespaces (except `kube-system` and `kube-public`) and looks after annotations in submitted pods. If you want to strictly control the list of namespaces where injection is allowed, set value `mutatingwebhook.namespaceSelector.boolean=true` when installing the chart as follows: