forked from Dynatrace/dynatrace-operator
-
Notifications
You must be signed in to change notification settings - Fork 0
/
multipleDynakubes.yaml
138 lines (124 loc) · 5.04 KB
/
multipleDynakubes.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
name: dynakube-application-monitoring
namespace: dynatrace
# Automatically connect the kubernetes api to the dynatrace tenant endpoint to enable kubernetes monitoring.
annotations:
feature.dynatrace.com/automatic-kubernetes-api-monitoring: "true"
spec:
# Dynatrace apiUrl including the `/api` path at the end.
# For SaaS, set `ENVIRONMENTID` to your environment ID.
# For Managed, change the apiUrl address.
# For instructions on how to determine the environment ID and how to configure the apiUrl address, see https://www.dynatrace.com/support/help/reference/dynatrace-concepts/environment-id/.
apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
# Optional: Name of the secret holding the credentials required to connect to the Dynatrace tenant
# If unset, the name of this custom resource is used
# For multiple Dynakube setup, each Dynakube can point to the same secret
#
# tokens: "my-secret"
# The namespaces which should be injected into
# If unset, all namespace will be injected into
# namespaceSelector has no effect on hostMonitoring or classicFullstack
# For examples regarding namespaceSelectors, see https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#resources-that-support-set-based-requirements
#
namespaceSelector:
matchLabels:
monitor: applicationMonitoring
# Configuration for OneAgent instances
#
oneAgent:
# Enables application-only monitoring and changes its settings
# Cannot be used in conjunction with cloud-native fullstack monitoring, classic fullstack monitoring or host monitoring
#
applicationMonitoring:
# Optional: If you want to use CSIDriver; disable if your cluster does not have 'nodes' to fall back to the volume approach.
# Defaults to false
#
useCSIDriver: true
# Configuration for ActiveGate instances.
#
activeGate:
# Specifies which capabilities will be enabled on ActiveGate instances
capabilities:
- kubernetes-monitoring
# Optional: Sets how many ActiveGate pods are spawned by the StatefulSet
# Defaults to "1"
#
replicas: 3
# Optional: Specifies resource settings for ActiveGate instances
# Consumption of the ActiveGate heavily depends on the workload to monitor
# The values should be adjusted according to the workload
#
resources:
requests:
cpu: 500m
memory: 512Mi
limits:
cpu: 1000m
memory: 1.5Gi
---
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
name: dynakube-cloud-native
namespace: dynatrace
spec:
# Dynatrace apiUrl including the `/api` path at the end.
# For SaaS, set `YOUR_ENVIRONMENT_ID` to your environment ID.
# For Managed, change the apiUrl address.
# For instructions on how to determine the environment ID and how to configure the apiUrl address, see https://www.dynatrace.com/support/help/reference/dynatrace-concepts/environment-id/.
apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
# Optional: Name of the secret holding the credentials required to connect to the Dynatrace tenant
# If unset, the name of this custom resource is used
# For a multiple Dynakube setup, each Dynakube can point to the same secret as it is reused
#
# tokens: "my-secret"
# The namespaces which should be injected into
# If unset, all namespace will be injected into
# namespaceSelector has no effect on hostMonitoring or classicFullstack
# For examples regarding namespaceSelectors, see https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#resources-that-support-set-based-requirements
#
namespaceSelector:
matchLabels:
monitor: cloudNativeFullStack
# Configuration for OneAgent instances
#
oneAgent:
# Enables cloud-native fullstack monitoring and changes its settings
# Cannot be used in conjunction with classic fullstack monitoring, application-only monitoring or host monitoring
#
cloudNativeFullStack:
# Optional: Specifies tolerations to include with the OneAgent DaemonSet.
# For more information on tolerations, see https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
#
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/master
operator: Exists
- effect: NoSchedule
key: node-role.kubernetes.io/control-plane
operator: Exists
# Configuration for ActiveGate instances.
#
activeGate:
# Specifies which capabilities will be enabled on ActiveGate instances
#
capabilities:
- routing
- dynatrace-api
# Optional: Sets how many ActiveGate pods are spawned by the StatefulSet
# Defaults to "1"
#
replicas: 2
# Optional: Specifies resource settings for ActiveGate instances
# Consumption of the ActiveGate heavily depends on the workload to monitor
# The values should be adjusted according to the workload
#
resources:
requests:
cpu: 500m
memory: 512Mi
limits:
cpu: 1000m
memory: 1.5Gi