jetstack / jetstack/jetstack-secure

feat: Add ability to input a completely custom agent configuration to chart

Offen
#418 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
helm kind/feature
Vorherrschende Sprache
Go
Sterne
262
Forks
27
Ø Merge
2 T. 7 Std.
Gemergte PRs (30 T.)
19

Beschreibung

Currently the config section is written to be helpful and auto template the required yaml based on either default or a list of resources. [See here](https://github.com/jetstack/jetstack-secure/blob/master/deploy/charts/jetstack-agent/values.yaml#L74-L85).

```yaml
# Configuration section for the agent itself
config:
# Can override the server if using a proxy between agent and Jetstack Secure
server: "https://platform.jetstack.io"
# REQUIRED - Your Jetstack Secure Organisation Name
organisation: ""
# REQUIRED - Your Jetstack Secure Cluster Name
cluster: ""
period: "0h1m0s"
dataGatherers:
default: true
custom: []
```

If we need to customise this to say namespaces for certain resource, that isn't currently possible.

A better trade of might be to just provide an option to use a customer configmap, or embed the entire config file and ignore the presets.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start with the linked deploy/charts/jetstack-agent/values.yaml config section at lines 74-85, then trace how the chart renders the agent configuration. Compare the custom ConfigMap and embedded-config options described in the issue, and verify the selected approach by rendering the chart with a fully custom configuration. Done means arbitrary resource-specific settings can be supplied without the current presets.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
kubernetes
Bereich
devops, infrastructure
Issue-Typ
Feature
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.