Skip to content
Merged
Changes from all commits
Commits
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
34 changes: 24 additions & 10 deletions pages/getting-started/advanced-config/sandboxing.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,19 +91,16 @@ A starter values file for configuring images for your console in the management

```yaml
# configure main console image
image:
repository: your.enterprise.registry/pluralsh/console
tag: 0.8.7 # only if you want to pin a tag (not recommended as it's set by the chart already)
# configure console operator image
controller:
controllerManager:
manager:
image:
repository: your.enterprise.registry/pluralsh/console
global:
registry: your.enterprise.registry
# configure kas image
kas:
agent:
proxy:
image:
repository: your.enteprise.registry/some/nginx
image:
repository: your.enterprise.registry/pluralsh/kas
```
Expand All @@ -123,6 +120,23 @@ agentk:

For more advanced configuration, we definitely recommend consulting the charts directly, they're both open source at https://github.com/pluralsh/console and https://github.com/pluralsh/deployment-operator.

## Disable cert-manager based TLS

Our chart defaults to including TLS reconciled by cert-manager, but if you use a cloud-integrated cert management tool like Amazon Certificate Manager, it is unnecessary and could cause double-encryption. Disabling is a simple values override, done with:

```yaml
# main plural ingress
ingress:
tls:
enabled: false
# disable for KAS ingress too
kas:
ingress:
tls:
enabled: false
```

## Configuring Agent Helm Values

Like we said, the main console deployment is pretty easy to configure, but the agents need to be handled specially since they need to be configured in bulk. We provide a number of utilities to make reconfiguration scalable.
Expand Down
Loading