Allow for existing Secrets instead of passing through the values.yaml

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm
Domain
devops

Research direction

Start by inspecting values.yaml and the Helm chart's secret handling. Determine how Redis and agent secrets are currently passed through the values, then define the chart configuration needed to use existing secrets instead. Done means installations can reference existing secrets without requiring their values in values.yaml.

Written by the indexing model from the issue text.

Description

Could we disable secrets from the helm chart so we don't need to include redis secrets or the agent secret?

Dominant language
Mustache
Stars
0
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from harness/gitops-helm-byoa

All issues in harness/gitops-helm-byoa

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.