-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add data collection configuration for Kubernetes #147
Conversation
Also add language around Splunk Observability versus Platform
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.
LGTM
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
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.
Looks good. Left a nit-picky suggestion.
Q: Do we want to specify k8s API namespace(s) here? These are used whenever we install any custom resource definition in a k8s cluster. For example, the operator today uses o11y.splunk.com
as the API namespace for Otel deployments. Do we want to prescribe this or out of scope for this PR? ref: https://github.com/signalfx/splunk-otel-collector-operator/blob/main/docs/splunkotelagent_cr_spec.md#splunkotelagent-custom-resource-specification
Also add language around Splunk Observability versus Platform