-
Notifications
You must be signed in to change notification settings - Fork 104
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
[CECO-1240] Rename profile label key #1230
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1230 +/- ##
=======================================
Coverage 55.32% 55.33%
=======================================
Files 241 241
Lines 27889 27889
=======================================
+ Hits 15430 15432 +2
+ Misses 11587 11586 -1
+ Partials 872 871 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report in Codecov by Sentry.
|
9f587f1
to
b5feb95
Compare
* Rename profile label key * Remove old profile label * Review suggestions
What does this PR do?
agent.datadoghq.com/profile
toagent.datadoghq.com/datadogagentprofile
<namespace>-<name>
, e.g.agent.datadoghq.com/datadogagentprofile:dap-test
instead ofagent.datadoghq.com/profile:default-dap-test
datadogagentprofile
anddatadogagentprofile_namespace
instead ofname
andnamespace
in profile-specific logs so they are more useful in the logs uiMotivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Minimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
a. Spin up <1.8.0 operator version with profiles enabled:
helm install operator --set image.tag="1.6.0" --set datadogAgentProfile.enabled=true datadog/datadog-operator
b. Deploy DDA and DAP
c. Check that the agent pod, ds, ds pod template spec, and node have the old label key and value
agent.datadoghq.com/profile:<profile-ns>-<profile-name>
and that the nodeaffinity for the default daemonset (ds that doesn't have the namexxx-with-profile-<profile-ns>-<profile-name>
) has an expression for theagent.datadoghq.com/profile
keyd. Upgrade the operator to 1.8.0+
e. Check that the agent pod, ds, ds pod template spec, and node have the new label key and value
agent.datadoghq.com/datadogagentprofile:<profile-name>
and that the nodeaffinity for the default daemonset has an expression for theagent.datadoghq.com/datadogagentprofile
keya. Delete the profile
b. Check that the agent pods, ds, and nodes don't have any profile label. The default daemonset should still have a nodeaffinity expression for the
agent.datadoghq.com/datadogagentprofile
keyExample label and nodeaffinity expression (for <1.8.0):
Example label and nodeaffinity expression (for 1.8.0+):
datadogagentprofile
anddatadogagentprofile_namespace
instead ofname
andnamespace
Checklist
bug
,enhancement
,refactoring
,documentation
,tooling
, and/ordependencies
qa/skip-qa
label