Skip to content

Docs for using Secret to store custom CA #2742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 16, 2024
Merged

Docs for using Secret to store custom CA #2742

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 22 additions & 4 deletions docs/vendor/replicated-sdk-customizing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,13 +116,15 @@ replicated:

## Custom Certificate Authority

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.
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 or a Secret prior to installation and providing appropriate values during installation.

To store the CA in a ConfigMap:
### Using a ConfigMap

1. Create a ConfigMap with the name of `private-ca` and the CA as the data value:
To use a CA stored in a ConfigMap:

1. Create a ConfigMap and the CA as the data value. Note that name of the ConfigMap and data key can be anything.
```bash
kubectl create configmap -n <NAMESPACE> private-ca --from-file=ca.crt=./ca.crt
kubectl -n <NAMESPACE> create configmap private-ca --from-file=ca.crt=./ca.crt
```
1. Add the name of the config map to the values file:
```yaml
Expand All @@ -134,6 +136,22 @@ To store the CA in a ConfigMap:
If the `--private-ca-configmap` flag is used with the [kots install](/enterprise/installing-existing-cluster-automation) command, this value will be populated in the Replicated SDK automatically.
:::

### Using a Secret

To use a CA stored in a Secret:

1. Create a Secret and the CA as a data value. Note that the name of the Secret and the key can be anything.
```bash
kubectl -n <NAMESPACE> create secret generic private-ca --from-file=ca.crt=./ca.crt
```
1. Add the name of the secret and the key to the values file:
```yaml
replicated:
privateCASecret:
name: private-ca
key: ca.crt
```

## Add Tolerations

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/).
Expand Down