Skip to content

[helm] add option to specify an existingSecret or a specific nodePort#174

Open
fbuchmeier wants to merge 7 commits intoPlace1:masterfrom
fbuchmeier:master
Open

[helm] add option to specify an existingSecret or a specific nodePort#174
fbuchmeier wants to merge 7 commits intoPlace1:masterfrom
fbuchmeier:master

Conversation

@fbuchmeier
Copy link
Copy Markdown

@fbuchmeier fbuchmeier commented Mar 12, 2022

  1. admin username, password and privatekey can be read from an external secret, to allow the use of for the sealed-secrets controller or external-secrets.

  2. option to specify a specific node port in case service.type = "NodePort" is used. Useful on bare metal deployments where no loadbalancer is available.

Signed-off-by: Florian Buchmeier flo_buchmeier@web.de

@fbuchmeier fbuchmeier changed the title add option to specify an existingSecret [helm] add option to specify an existingSecret Mar 12, 2022
…pected 'array'

Signed-off-by: Florian Buchmeier <flo_buchmeier@web.de>
Signed-off-by: Florian Buchmeier <flo_buchmeier@web.de>
@fbuchmeier fbuchmeier changed the title [helm] add option to specify an existingSecret [helm] add option to specify an existingSecret or a specific nodePort Mar 12, 2022
DasSkelett pushed a commit to DasSkelett/wg-access-server that referenced this pull request Aug 2, 2022
…n/website/types/react-dom-18.0.3

Bump @types/react-dom from 17.0.11 to 18.0.3 in /website
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants