You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: charts/agent-control/README.md
+21-6
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,20 @@ means that it honors a wide range of defaults and globals common to most New Rel
26
26
Options that can be defined globally include `affinity`, `nodeSelector`, `tolerations`, `proxy` and others. The full list can be found at
27
27
[user's guide of the common library](https://github.com/newrelic/helm-charts/blob/master/library/common-library/README.md).
28
28
29
+
## Flux Integration
30
+
31
+
Agent Control leverages [Flux](https://github.com/fluxcd/flux2) custom resources to automate the deployment of New Relic agents. This chart includes Flux as a dependency by default, eliminating the need for separate installation.
32
+
33
+
### Using an Existing Flux Installation
34
+
35
+
To use an existing Flux setup, disable the default installation by setting `flux2.enabled` to `false` in your values. Ensure your existing Flux installation meets the following requirements:
36
+
37
+
- Agent control is compatible with **Flux Versions**: 2.3.x, 2.4.x, or 2.5.x.
38
+
-**CRDs Required**:
39
+
-`source.toolkit.fluxcd.io/v1` for HelmRepository
40
+
-`helm.toolkit.fluxcd.io/v2` for HelmRelease
41
+
-**Namespace Access**: Must be configured to watch resources in the `newrelic` namespace, or the namespace where Agent Control is deployed.
42
+
29
43
## Test custom agentTypes
30
44
31
45
In order to test custom agentTypes is possible to leverage `extraVolumeMounts` and `extraVolumes` once you have created the configMap in the namespace.
@@ -72,12 +86,12 @@ As of the creation of the chart, it has no particularities and this section can
72
86
| agent-control-deployment.config.agentControl.content | object | `{}` | Overrides the configuration that has been created automatically by the chart. This configuration here will be **MERGED** with the configuration specified above. If you need to have you own configuration, disabled the creation of this configMap and create your own. |
73
87
| agent-control-deployment.config.agentControl.create | bool | `true` | Set if the configMap is going to be created by this chart or the user will provide its own. |
74
88
| agent-control-deployment.config.fleet_control.auth.organizationId | string | `""` | Organization ID where fleets will live. |
75
-
| agent-control-deployment.config.fleet_control.auth.secret.client_id.base64 | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set client ID directly as base64. This options is mutually exclusive with `plain`. |
76
-
| agent-control-deployment.config.fleet_control.auth.secret.client_id.plain | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set client ID directly as plain text. This options is mutually exclusive with `base64`. |
89
+
| agent-control-deployment.config.fleet_control.auth.secret.client_id.base64 | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set client ID directly as base64 if you want to skip its creation. This options is mutually exclusive with `plain`. |
90
+
| agent-control-deployment.config.fleet_control.auth.secret.client_id.plain | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set client ID directly as plain text if you want to skip its creation. This options is mutually exclusive with `base64`. |
77
91
| agent-control-deployment.config.fleet_control.auth.secret.client_id.secret_key | string | `client_id` | Key inside the secret containing the client ID. |
78
92
| agent-control-deployment.config.fleet_control.auth.secret.name | string | release name suffixed with "-auth" | Name auth' secret provided by the user. If the creation of this secret is set to `true`, this is the same the secret will have. |
79
-
| agent-control-deployment.config.fleet_control.auth.secret.private_key.base64_pem | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set private key directly as base64. This options is mutually exclusive with `plain_pem`. |
80
-
| agent-control-deployment.config.fleet_control.auth.secret.private_key.plain_pem | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set private key directly as plain text. This options is mutually exclusive with `base64_pem`. |
93
+
| agent-control-deployment.config.fleet_control.auth.secret.private_key.base64_pem | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set private key directly as base64 if you want to skip its creation. This options is mutually exclusive with `plain_pem`. |
94
+
| agent-control-deployment.config.fleet_control.auth.secret.private_key.plain_pem | string | `nil` | In case `.config.auth.secret.create` is true, you can set these keys to set private key directly as plain text if you want to skip its creation. This options is mutually exclusive with `base64_pem`. |
81
95
| agent-control-deployment.config.fleet_control.auth.secret.private_key.secret_key | string | `private_key` | Key inside the secret containing the private key. |
82
96
| agent-control-deployment.config.fleet_control.enabled | bool | `true` | Enables or disables the auth against fleet control. It implies to disable any fleet communication and running the agent in stand alone mode where only the agents specified on `.config.subAgents` will be launched. |
83
97
| agent-control-deployment.config.fleet_control.fleet_id | string | `""` | Specify a fleet_id to automatically connect the Agent Control to an existing fleet. |
@@ -95,12 +109,13 @@ As of the creation of the chart, it has no particularities and this section can
95
109
| agent-control-deployment.extraVolumes | list | `[]` | Volumes to mount in the containers |
96
110
| agent-control-deployment.fedramp.enabled | bool | `false` | TODO: Enables FedRAMP. Can be configured also with `global.fedramp.enabled` |
97
111
| agent-control-deployment.hostNetwork | bool | `false` | Sets pod's hostNetwork. Can be configured also with `global.hostNetwork` |
| agent-control-deployment.labels | object | `{}` | Additional labels for chart objects. Can be configured also with `global.labels` |
103
117
| agent-control-deployment.licenseKey | string | `""` | This set this license key to use. Can be configured also with `global.licenseKey` |
118
+
| agent-control-deployment.nameOverride | string | `"agent-control"` | Override the name of the chart used to template resource names. |
104
119
| agent-control-deployment.nodeSelector | object | `{}` | Sets pod's node selector. Can be configured also with `global.nodeSelector` |
105
120
| agent-control-deployment.nrStaging | bool | `false` | Send the metrics to the staging backend. Requires a valid staging license key. Can be configured also with `global.nrStaging` |
106
121
| agent-control-deployment.podAnnotations | object | `{}` | Annotations to be added to all pods created by the integration. |
Copy file name to clipboardexpand all lines: charts/agent-control/README.md.gotmpl
+14
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,20 @@ means that it honors a wide range of defaults and globals common to most New Rel
31
31
Options that can be defined globally include `affinity`, `nodeSelector`, `tolerations`, `proxy` and others. The full list can be found at
32
32
[user's guide of the common library](https://github.com/newrelic/helm-charts/blob/master/library/common-library/README.md).
33
33
34
+
## Flux Integration
35
+
36
+
Agent Control leverages [Flux](https://github.com/fluxcd/flux2) custom resources to automate the deployment of New Relic agents. This chart includes Flux as a dependency by default, eliminating the need for separate installation.
37
+
38
+
### Using an Existing Flux Installation
39
+
40
+
To use an existing Flux setup, disable the default installation by setting `flux2.enabled` to `false` in your values. Ensure your existing Flux installation meets the following requirements:
41
+
42
+
- Agent control is compatible with **Flux Versions**: 2.3.x, 2.4.x, or 2.5.x.
43
+
- **CRDs Required**:
44
+
- `source.toolkit.fluxcd.io/v1` for HelmRepository
45
+
- `helm.toolkit.fluxcd.io/v2` for HelmRelease
46
+
- **Namespace Access**: Must be configured to watch resources in the `newrelic` namespace, or the namespace where Agent Control is deployed.
47
+
34
48
## Test custom agentTypes
35
49
36
50
In order to test custom agentTypes is possible to leverage `extraVolumeMounts` and `extraVolumes` once you have created the configMap in the namespace.
Copy file name to clipboardexpand all lines: charts/agent-control/charts/agent-control-deployment/templates/preinstall-job-register-system-identity.yaml
Copy file name to clipboardexpand all lines: charts/nr-ebpf-agent/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ Options that can be defined globally include `affinity`, `nodeSelector`, `tolera
90
90
| ebpfAgent.containerSecurityContext | object |`{}`| Sets ebpfAgent pod containerSecurityContext. Overrides `containerSecurityContext` and `global.securityContext.container`|
91
91
| ebpfAgent.image.pullPolicy | string |`"IfNotPresent"`| The pull policy is defaulted to IfNotPresent, which skips pulling an image if it already exists. If pullPolicy is defined without a specific value, it is also set to Always. |
92
92
| ebpfAgent.image.repository | string |`"docker.io/newrelic/newrelic-ebpf-agent"`| eBPF agent image to be deployed. |
93
-
| ebpfAgent.image.tag | string |`"agent-nr-ebpf-agent_0.0.7"`| The tag of the eBPF agent image to be deployed. |
93
+
| ebpfAgent.image.tag | string |`"agent-nr-ebpf-agent_0.0.8"`| The tag of the eBPF agent image to be deployed. |
94
94
| ebpfAgent.podAnnotations | object |`{}`| Sets ebpfAgent pod Annotations. Overrides `podAnnotations` and `global.podAnnotations`|
95
95
| ebpfAgent.podSecurityContext | object |`{}`| Sets ebpfAgent pod podSecurityContext. Overrides `podSecurityContext` and `global.securityContext.pod`|
96
96
| ebpfAgent.resources.limits.memory | string |`"2Gi"`| Max memory allocated to the container. |
@@ -99,7 +99,7 @@ Options that can be defined globally include `affinity`, `nodeSelector`, `tolera
99
99
| ebpfAgent.tolerations | list |`[]`| Sets ebpfAgent pod tolerations. Overrides `tolerations` and `global.tolerations`|
100
100
| ebpfClient.image.pullPolicy | string |`"IfNotPresent"`| The pull policy is defaulted to IfNotPresent, which skips pulling an image if it already exists. If pullPolicy is defined without a specific value, it is set to Always. |
101
101
| ebpfClient.image.repository | string |`"docker.io/newrelic/newrelic-ebpf-agent"`| eBPF client image to be deployed. |
102
-
| ebpfClient.image.tag | string |`"client-nr-ebpf-client_0.0.11"`| The tag of the eBPF client image to be deployed. |
102
+
| ebpfClient.image.tag | string |`"client-nr-ebpf-client_0.0.12"`| The tag of the eBPF client image to be deployed. |
103
103
| ebpfClient.resources.limits.memory | string |`"100Mi"`| Max memory allocated to the container. |
104
104
| ebpfClient.resources.requests.cpu | string |`"50m"`| Min CPU allocated to the container. |
105
105
| ebpfClient.resources.requests.memory | string |`"50Mi"`| Min memory allocated to the container. |
Copy file name to clipboardexpand all lines: charts/nr-ebpf-agent/values.yaml
+3-3
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ customSecretLicenseKey: ""
10
10
# -- If using a customSecretLicenseKey, you must supply your region "US"/"EU". Otherwise, leave this value as an empty string.
11
11
region: ""
12
12
# -- Enable to export data to NR's Staging otel endpoint (staging-otlp.nr-data.net:4317).
13
-
nrStaging:false
13
+
nrStaging:
14
14
# -- Configures the agent to send all data through the proxy specified via the otel collector.
15
15
proxy: ""
16
16
# -- Drop data when service names map to an IP address.
@@ -103,7 +103,7 @@ ebpfAgent:
103
103
# -- The pull policy is defaulted to IfNotPresent, which skips pulling an image if it already exists. If pullPolicy is defined without a specific value, it is also set to Always.
104
104
pullPolicy: IfNotPresent
105
105
# -- The tag of the eBPF agent image to be deployed.
106
-
tag: agent-nr-ebpf-agent_0.0.7
106
+
tag: agent-nr-ebpf-agent_0.0.8
107
107
resources:
108
108
limits:
109
109
# -- Max memory allocated to the container.
@@ -132,7 +132,7 @@ ebpfClient:
132
132
# -- The pull policy is defaulted to IfNotPresent, which skips pulling an image if it already exists. If pullPolicy is defined without a specific value, it is set to Always.
133
133
pullPolicy: IfNotPresent
134
134
# -- The tag of the eBPF client image to be deployed.
0 commit comments