-
Notifications
You must be signed in to change notification settings - Fork 330
Closed as not planned
Labels
kind/enhancementAn entirely new featureAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committedPriority has not yet been determined; a good signal that maintainers aren't fully committedstaleStalled with a lack of maintainer commitment; Likely to be closed to reduce noise in the issue queueStalled with a lack of maintainer commitment; Likely to be closed to reduce noise in the issue queue
Description
Checklist
- I've searched the issue queue to verify this is not a duplicate feature request.
- I've pasted the output of
kargo version, if applicable. - I've pasted logs, if applicable.
Proposed Feature
Allow for easier passing of urls instead of requirement to redeploy whole helm chart. E.g. looking for secrets with specific labels.
Motivation
With sharded architecture, onboarding new shard requires redeployment of the kargo chart on hub to load additional argocd url. This could be simplified with secrets as those can be created and deleted much easier, without adding the need to redeploy whole app.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/enhancementAn entirely new featureAn entirely new featurekind/proposalIndicates maintainers have not yet committed to a feature requestIndicates maintainers have not yet committed to a feature requestneeds/areaIssue or PR needs to be labeled to indicate what parts of the code base are affectedIssue or PR needs to be labeled to indicate what parts of the code base are affectedneeds/priorityPriority has not yet been determined; a good signal that maintainers aren't fully committedPriority has not yet been determined; a good signal that maintainers aren't fully committedstaleStalled with a lack of maintainer commitment; Likely to be closed to reduce noise in the issue queueStalled with a lack of maintainer commitment; Likely to be closed to reduce noise in the issue queue