The AWS Observability Helm Charts repository contains Helm charts to provide easy mechanisms to setup the CloudWatch Agent and other collection agents to collect telemetry data such as metrics, logs and traces to send to AWS monitoring services.
Apache License 2.0
8
stars
14
forks
source link
Create separate agent daemonsets on windows for container insights and application signals #90
We need host networking to have the agent run as a host process container to retrieve container insights metrics from HCS (Host Compute Service).
In order to allow container insights and application signals, we need 2 daemonsets for windows. One running as a host process container, and another that is not.
This PR introduces a a new daemonset specifically for container insights cloudwatch-agent-windows-container-insights, and the current cloudwatch-agent-windows will be used for application signals.
This PR also addressing missing cluster name in the windows configs
Issue #, if available: N/A
Description of changes: Currently, kubernetes networking is not supported on windows containers with host networking:
From https://kubernetes.io/docs/concepts/services-networking/windows-networking/
We need host networking to have the agent run as a host process container to retrieve container insights metrics from HCS (Host Compute Service).
In order to allow container insights and application signals, we need 2 daemonsets for windows. One running as a host process container, and another that is not.
This PR introduces a a new daemonset specifically for container insights
cloudwatch-agent-windows-container-insights
, and the currentcloudwatch-agent-windows
will be used for application signals.This PR also addressing missing cluster name in the windows configs
Testing Ran helm template:
Pods:
services
AmazonCloudWatchAgent resources
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.