Skip to content
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.

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

Dynamically use helm release-name for Kubernetes resources #50

Open
3 tasks
MfCrizz opened this issue Jun 19, 2023 · 0 comments
Open
3 tasks

Dynamically use helm release-name for Kubernetes resources #50

MfCrizz opened this issue Jun 19, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@MfCrizz
Copy link
Contributor

MfCrizz commented Jun 19, 2023

Currently "unguard" is hard coded in many parts of the helm chart.

Use the helm release-name instead.
The helm release name can be referenced in the chart using the function {{- include "unguard.fullname" -}}
If ungaurd services (e.g. envoy-proxy) also use a hard-coded name, update service to specify the name via an environment variable.

Definition of Done

  • All Kubernetes resources and application services use the helm release-name.

Tasks

  • Update the Chart to use the helm release-name
  • Update ungaurd services to use the helm release-name
@MfCrizz MfCrizz added the enhancement New feature or request label Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant