- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
The Datadog Cluster Agent manages the Datadog Admission Controller by creating, updating, and deleting Admission Controllers as needed. To disable the Admission Controller or remove the Cluster Agent, you must first disable the Admission Controller features in the Cluster Agent configuration and redeploy the Cluster Agent. Once the Admission Controllers are removed, the Cluster Agent can be safely removed if necessary.
Datadog Cluster Agent v7.63+
To disable the Admission Controllers with your Cluster Agent managed by the Datadog Operator:
features.admissionController.enabled
to true
in your DatadogAgent
configuration.features.admissionController.validation.enabled
to false
in your DatadogAgent
configuration.features.admissionController.mutation.enabled
to false
in your DatadogAgent
configuration. apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
name: datadog
spec:
features:
admissionController:
enabled: true
validation:
enabled: false
mutation:
enabled: false
Note: The the features.admissionController.enabled
parameter is set to true
to allow the Cluster Agent to manage the Kubernetes Admission Controllers.
After redeploying the Cluster Agent with the updated configuration, the Admission Controllers are removed.
To disable the Admission Controllers with your Cluster Agent managed by the Datadog Helm Chart:
clusterAgent.admissionController.enabled
to true
.clusterAgent.admissionController.validation.enabled
to false
.clusterAgent.admissionController.mutation.enabled
to false
.clusterAgent:
enabled: true
admissionController:
enabled: true
validation:
enabled: false
mutation:
enabled: false
You can confirm the Admission Controllers are removed by checking ValidatingWebhookConfiguration
and MutatingWebhookConfiguration
resources in your cluster.
kubectl get validatingwebhookconfigurations.admissionregistration.k8s.io
kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io