-
Notifications
You must be signed in to change notification settings - Fork 53
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
Adding V3 compatible windows integration #744
Conversation
Signed-off-by: RagalahariP <rpotti@newrelic.com>
f55ab87
to
d1fb110
Compare
licenseKey: <> | ||
cluster: <> | ||
|
||
kubelet: |
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 this be in values.yaml
? i don't see it being imported anywhere
charts/newrelic-infrastructure/templates/kubelet/daemonset-windows.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: RagalahariP <rpotti@newrelic.com>
Signed-off-by: RagalahariP <rpotti@newrelic.com>
Signed-off-by: RagalahariP <rpotti@newrelic.com>
…ri-kubernetes into V3-windows-support
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.
lgtm. i dont have merge permission for this repo but also we should get a second pair of eyes on this. ill ping the team
# Reference yaml for Windows V3 integration | ||
|
||
global: | ||
licenseKey: <> |
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.
are those needed? i imagine we can get the keys from values.yaml
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.
@RagalahariP can you address this comment? I'm not sure this is needed.
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.
@htroisi Yes, I have deleted redundant values-windows.yaml . Now values.yaml has windows config option.
actually i just noticed the tests are failing. not sure if it's specific to this branch since I see other PRs failing |
cluster: <> | ||
|
||
kubelet: | ||
enableWindows: true |
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 we upstream enableWindows
and windowsOsList
in the chart's values.yaml and README file?
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.
Updated
@RagalahariP I DM'd you the instructions to get the E2E tests to pass. |
@@ -130,6 +130,16 @@ kubelet: | |||
scraperMaxReruns: 4 | |||
# port: | |||
# scheme: | |||
# Set enableWindows to true to enable monitoring on Windows nodes |
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.
Could you modify the comments for enableWindows
and enableWindows
to use the same formatting as the rest of the file?
Once you've modified the formatting can you run helm-docs
tool to automatically update the README.md file?
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.
Updated with helm-docs
Signed-off-by: RagalahariP <rpotti@newrelic.com>
Signed-off-by: RagalahariP <rpotti@newrelic.com>
Signed-off-by: RagalahariP <rpotti@newrelic.com>
Closing this PR is favor of #754 since E2E tests don't work from forks. |
Testing : Tested in local EKS cluster with the following node config
Dashboard: https://onenr.io/0BQ18La75jx