-
Notifications
You must be signed in to change notification settings - Fork 7
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 cluster events deployment to agent stack #156
Conversation
ca6a820
to
e53bf06
Compare
The following chart updates are necessary:
|
5f82ce6
to
b015972
Compare
fullnameOverride: "observe" | ||
namespaceOverride: "observe" | ||
nameOverride: "daemonset" | ||
namespaceOverride: "k8sexplorer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we switching namespaceOverride
?
path: "observe-agent.yaml" | ||
defaultMode: 420 | ||
|
||
extraVolumeMounts: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Injecting our otel collector config as volume
key: id | ||
extraEnvsFrom: [] | ||
extraVolumes: | ||
- name: "observe-agent-deployment-config" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
injecting the observe-agent.yaml as volume
requests: | ||
cpu: 250m | ||
memory: 256Mi | ||
daemonset: | ||
daemonset: | ||
# Resource settings | ||
resources: | ||
limits: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for removing these! It will likely reduce some pain for now. Eventually we can provide a config, but that's for later.
- {name: serviceaccounts, mode: watch} | ||
processors: | ||
# needs to come after transform/watch_objects in pipelines | ||
observek8sattributes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this is the new custom processor.
But yeah the current config.tpl format LGTM. Once we start iterating on it we can have more feedbacks
| deployment-cluster-events.clusterRole.clusterRoleBinding.name | string | `""` | | | ||
| deployment-cluster-events.clusterRole.create | bool | `true` | | | ||
| deployment-cluster-events.clusterRole.name | string | `""` | | | ||
| deployment-cluster-events.clusterRole.rules[0].apiGroups[0] | string | `""` | | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a little painful...
I guess it's so that we allow customer to restrict the access for this agent easier?
(Either way this comment doesn't block this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is just the schema for the otel-collector
open source chart
No description provided.