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

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

Open
hawksight opened this issue Apr 14, 2023 · 0 comments
Labels
helm Bugs or features relating to the helm chart installation kind/feature Categorizes issue or PR as related to a new feature.

Comments

@hawksight
Copy link
Contributor

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.

# 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.

@hawksight hawksight changed the title feat: Add ability to input a completely custom agent configuration feat: Add ability to input a completely custom agent configuration to chart Apr 20, 2023
@hawksight hawksight added kind/feature Categorizes issue or PR as related to a new feature. helm Bugs or features relating to the helm chart installation labels Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
helm Bugs or features relating to the helm chart installation kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant