Skip to content

Commit 59631f6

Browse files
authored
Merge pull request #786 from snyk/docs/ca_certs
docs: add setting custom CA certs to README
2 parents b34b1c0 + 6ed0952 commit 59631f6

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

snyk-monitor/README.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ Proxying traffic through a forwarding proxy can be achieved by setting the follo
108108

109109
For example:
110110

111-
```bash
111+
```shell
112112
helm upgrade --install snyk-monitor snyk-charts/snyk-monitor \
113113
--namespace snyk-monitor \
114114
--set clusterName="Production cluster" \
@@ -121,7 +121,7 @@ Note that `snyk-monitor` does not proxy requests to the Kubernetes API server.
121121

122122
Note that `snyk-monitor` does not support wildcards or CIDR addresses in `no_proxy` -- it will only look for exact matches. For example:
123123

124-
```bash
124+
```shell
125125
# not ok:
126126
helm upgrade --install ... \
127127
--set no_proxy=*.example.local,*.other.global,192.168.0.0/16
@@ -140,7 +140,7 @@ To lower `snyk-monitor`'s logging verbosity `log_level` value could be set to on
140140
By default, `log_level` is `'INFO'`.
141141

142142
For example
143-
```bash
143+
```shell
144144
helm upgrade --install snyk-monitor snyk-charts/snyk-monitor \
145145
--namespace snyk-monitor \
146146
--set clusterName="Production cluster" \
@@ -173,7 +173,7 @@ Using PodSecurityPolicies can be achieved by setting the following values in the
173173
* psp.name - default is empty. Leave it empty if you want us to install the necessary PodSecurityPolicy. Modify it to specify an existing PodSecurityPolicy rather than creating a new one.
174174

175175
For example:
176-
```bash
176+
```shell
177177
helm upgrade --install snyk-monitor snyk-charts/snyk-monitor \
178178
--namespace snyk-monitor \
179179
--set clusterName="Production cluster" \
@@ -193,6 +193,11 @@ If you prefer to override this, you can add your own list of namespaces to exclu
193193
--set excludedNamespaces={kube-node-lease,kube-public,local-path-storage,some_namespace}
194194
```
195195

196+
## Using custom CA certificate
197+
You can provide custom CA certificates to use for validating TLS connections by adding them to a ConfigMap named snyk-monitor-certs. These additional certificates are used when pulling images from container registries.
198+
199+
If running Snyk on-prem, you can also use a custom CA certificate to validate the connection to kubernetes-upstream for sending scan results by providing the certificate under the following path in the ConfigMap: /srv/app/certs/ca.pem
200+
196201
## Upgrading
197202

198203
When upgrading the Snyk monitor, if you would like to reuse the last release's values and merge in any overrides from the command line via --set and -f, you can use the option `--reuse-values`. For example:

0 commit comments

Comments
 (0)