Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Conversation

@dmitchsplunk
Copy link
Contributor

Requirements

  • Content follows Splunk guidelines for style and formatting.
  • You are contributing original content.

Describe the change

When deploying the collector in a K8s cluster with both Linux and Windows nodes, where the operator is enabled, we need to add a node selector to ensure that the operator is deployed to a Linux node, as it will not work if deployed to a Windows node. I've tested this change in an AKS environment with Linux and Windows nodes.

When deploying the collector in a K8s cluster with both Linux and Windows nodes, where the operator is enabled, we need to add a node selector to ensure that the operator is deployed to a Linux node, as it will not work if deployed to a Windows node.
@dmitchsplunk dmitchsplunk requested a review from a team as a code owner March 28, 2025 14:16
@jcatera-splunk jcatera-splunk added the stop-alert Stops Slack notification in #o11y-docs-feedback so that PR can be worked wo unnecessary noise label Mar 28, 2025
@aurbiztondo-splunk aurbiztondo-splunk self-assigned this Mar 28, 2025
@aurbiztondo-splunk
Copy link
Contributor

Node support to be added to default config instead - see open-telemetry/opentelemetry-operator#642.

@aurbiztondo-splunk
Copy link
Contributor

Summary of tasks - https://splunk.atlassian.net/browse/O11YDOCS-7108

@aurbiztondo-splunk
Copy link
Contributor

Closing as discussed in the jira ticket.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

external gdi stop-alert Stops Slack notification in #o11y-docs-feedback so that PR can be worked wo unnecessary noise

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants