Skip to content

Commit b45df5a

Browse files
authored
Document custom CA use with replicated SDK (#2667)
1 parent b6a59de commit b45df5a

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/vendor/replicated-sdk-customizing.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -110,6 +110,22 @@ replicated:
110110
value: my-value-2
111111
```
112112
113+
## Custom Certificate Authority
114+
115+
When installing the Replicated SDK behind a proxy server that terminates TLS and injects a custom certificate, you must provide the CA to the SDK. This can be done by storing the CA in a ConfigMap prior to installation and setting `privateCAConfigmap` key to the name of the ConfigMap.
116+
117+
To store the CA in a ConfigMap:
118+
119+
1. Create a ConfigMap with the name of `private-ca` and the CA as the data value:
120+
```bash
121+
kubectl create configmap -n <NAMESPACE> private-ca --from-file=ca.crt=./ca.crt
122+
```
123+
1. Add the name of the config map to the values file:
124+
```yaml
125+
replicated:
126+
privateCAConfigmap: private-ca
127+
```
128+
113129
## Add Tolerations
114130

115131
The Replicated SDK provides a `replicated.tolerations` value that allows users to add custom tolerations to the deployment. For more information about tolerations, see [Taints and Tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/).

0 commit comments

Comments
 (0)