Advanced usage

Some edge use-cases might not have been included in the previous installation documentation, for clarity purposes. You may find some of them below.

Running behind a container registry proxy

If your installation environment requires you to whitelist images that can be pulled by the Kubernetes cluster, you must whitelist the registry.evertrust.io/stream and registry.evertrust.io/stream-upgrade images. It is then possible to override the images being pulled by setting the global.imageRegistry key in your values.yaml file to point to your private registry:

global:
  imageRegistry: <YOUR-PRIVATE-REGISTRY>

Leases

To ensure clustering issues get resolved as fast as possible, Stream can use Kubernetes leases. We strongly recommend that you use this safety mechanism. However, the feature can be disabled by setting the leases.enabled key to false.

Injecting extra configuration

Extra Stream configuration can be injected to the bundled application.conf file to modify low-level behavior of Stream. This should be used carefully as it may cause things to break. To do so, use the extraConfig value in your values.yaml file:

This can be done with the following edits to your values.yaml file:

extraConfig: |
    play.server.http.port = 9999
    stream {
      metrics.enabled = true
    }

Extra configurations are included at the end of the config file, overriding any previously set config value.

An exhaustive list of configuration options can be found on the Available technical configuration parameters page.