Skip to content

Feature Request: Allow extra objects to be deployed alonside server and client #61

Open
@gallolp

Description

@gallolp

Hi,

I am currently working to deploy an OPAL server instance and an OPAL client instance (cluster mode) as separate releases using the Helm chart.

I see there is an undocumented secrets parameter on both server and client sections of the value file, however there is no way to deploy those secrets or any additional objects in the same release using the chart.

It would be great to be able to deploy extra manifests using the same chart, use cases include:

  • Private and Public keys as secrets (instead of regular env) when running in secure mode
  • Client token as secret
  • Broadcast url as secret (it contains the DB/Redis password)
  • Any other manifests ie. Istio manifests, etc

If you are interested, I have prepared a PR that adds the following:

  • A new extraObjects parameter to the root section of the value file
  • Updated values JSON schema (array of string)
  • Allows templates inside the objects, they are defined as strings to avoid yaml parse errors on the value file and allow templating
  • Adds sample values to the value file

Thank you for you work on OPAL.

Edited: Updated to only add one extraObjects section.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions