emissary-ingress/emissary

ambassadorConfig is a left-over

Open

#3,295 opened on Jun 23, 2020

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)Python (679 forks)batch import
good first issuestalet:bug

Repository metrics

Stars
 (4,096 stars)
PR merge metrics
 (PR metrics pending)

Description

See this issue: https://github.com/datawire/ambassador/issues/1198

Apparently the ability to configure using a ConfigMap was removed some time ago, however, the chart still takes an ambassadorConfig value and creates a ConfigMap. Other than the above issue there seems to be no real documentation of what this is/was supposed to do.

Contributor guide

Research direction
Find the ConfigMap template in the Helm chart that uses ambassadorConfig, and remove it along with the values.yaml entry.
Tech stack
python
Domain
backendinfrastructure
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HelmKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75