-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NR-346357: Sync up nr-ebpf-agent charts in helm-charts from newrelic-… #1537
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to add the remaining changes from eBPF repo as well here to get this chart up to date?
@@ -131,3 +131,33 @@ nodeSelector: {} | |||
tolerations: [] | |||
# -- Sets all pods' affinities. Can be configured also with `global.affinity` | |||
affinity: {} | |||
# -- Kubernetes cluster domain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe you'll need to create new image & tags (need to use the dockerhub registry now since we are moving away from GCR) as well since the existing artifacts don't have the logic to utilize these configuration changes.
You'll also need to run helm-docs to auto-update the readme with the new changes from this Values.yaml
proxy: "" | ||
# -- Drop data when service names map to an IP address. | ||
# Drop data where to service names mapps to an IP address |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mapps
misspelling
apiVersion: apps/v1 | ||
kind: DaemonSet | ||
metadata: | ||
name: nr-ebpf-agent | ||
labels: | ||
{{- if gt .Chart.Version "0.1.14"}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this and all the other occurrences; Why are we checking this? This would make more sense if this "feature" was planned for a later release. Seems to me this conditional is not needed; though I could be wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this check in the latest commit.
We have added two labels, app and component, in the spec.selector section of the nr-ebpf-agent-service.yaml file. The Helm upgrade check is failing in the pull request (PR) due to these newly added labels, as Kubernetes does not allow changes to the spec.selector field of an existing Service. To pass the Helm upgrade check, we temporarily excluded the newly added labels from the spec.selector. This allowed all checks to pass in the PR. After the checks passed, we reverted the temporary changes and included the labels again in the latest commit. Given that the Helm upgrade check failure is due to the immutable nature of the spec.selector field, we can proceed with the changes by neglecting the Helm upgrade check. |
@@ -13,7 +13,7 @@ type: application | |||
# This is the chart version. This version number should be incremented each time you make changes | |||
# to the chart and its templates, including the app version. | |||
# Versions are expected to follow Semantic Versioning (https://semver.org/) | |||
version: 0.1.13 | |||
version: 0.1.14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will need to bump this again
# -- 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. | ||
pullPolicy: IfNotPresent | ||
# -- The tag of the eBPF agent image to be deployed. | ||
tag: 0.0.5 | ||
tag: nr-ebpf-agent_0.0.5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will need to create new images for the agent & client, the changes you are adding for TLS/Sampling/etc. are not present in these existing image tags so any of the respective configurations from the Helm chart will not be picked up by the containers
# -- 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. | ||
pullPolicy: IfNotPresent | ||
# -- The tag of the eBPF client image to be deployed. | ||
tag: 0.0.7 | ||
tag: nr-ebpf-client_0.0.7 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto here for image update
|
||
# -- The periodicity in seconds at which the eBPF agent pushes data to the OTel collector for export to NR. | ||
# The periodicity in seconds at which the eBPF client pushes data to the OTel collector for export to NR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be agent
here
# while tcp_stats tracks TCP metrics. | ||
stirlingSources: "socket_tracer,tcp_stats" | ||
# -- The protocols to enable for tracing in the socket_tracer. | ||
# while tcp_stats tracks TCP metrics and jvm_stats tracks JVM metrics. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to remove the jvm_stats
connector from the comment and environment variable since we are not exporting JVM data.
dropDataIpServiceNames: true | ||
# -- Drop data from the kube-system namespace. | ||
# Drop data from to the kube-system namespace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will need to prefix all of the relevant comments with --
. This is because the ReadMe's auto generation relies on that prefix in order to add the description.
The auto generation of the ReadMe is done by running helm-docs.
dropDataIpServiceNames: true | ||
# -- Drop data from the kube-system namespace. | ||
# Drop data from to the kube-system namespace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Drop data from to the kube-system namespace | |
# -- Drop data from the kube-system namespace. |
…ebpf-agent
Is this a new chart
What this PR does / why we need it:
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[mychartname]
)