-
Notifications
You must be signed in to change notification settings - Fork 247
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
Add helm values to configure hostNetwork and additional env vars #1878
Add helm values to configure hostNetwork and additional env vars #1878
Conversation
✅ Deploy Preview for kubernetes-sigs-nfd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -478,6 +482,8 @@ topologyUpdater: | |||
enable: false | |||
args: [] | |||
createCRDs: false | |||
additionalEnvs: [] |
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.
My only comment on this PR would be the name of this Var. maybe envs
is just ok?
/assign @marquiz
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.
Also thought about this, but there are already envs in the container. The name additionalEnvs
makes it more explicit that those are additional env vars IMO. Also okay to rename it to envs
, no hard opinion here
Edit: but if we take a look at args
it is the same; there are already args set but the helm value args
is for additional arguments. Will rename it.
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.
Yeah, sorry about the hassle. I regret my original PR adding args
. But now that's changed
221ce95
to
b545d02
Compare
args: [] | ||
envs: [] |
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.
Looking at this now, I'd prefer name extraEnvs
.
I know envs
is in line with args
. I recall that I have myself added the args
and I don't like the name 🙄. I'd suggest I rename that to extraArgs
(in a separate PR) and you rename to extraEnvs
in this PR.
WDYT?
Nevertheless,we need to document the new values in docs/deployment/helm.md
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.
Renamed to extraEnvs
, rebased and updated the helm documentation
5861141
to
64ae839
Compare
@tobiasgiese: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
64ae839
to
9db207c
Compare
9db207c
to
025fc5f
Compare
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.
Wouldn't we need this for nfd-gc, too?
025fc5f
to
4f756b7
Compare
We have to run our NFD workers in the host network. Also we need additional env variables such as KUBERNETES_SERVICE_HOST and _PORT. To achieve this we can simply add generic helm values. The default behavior is not changed. Signed-off-by: Tobias Giese <[email protected]>
4f756b7
to
af0592b
Compare
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.
Thank you @tobiasgiese for the improvement. This looks good to me, now
/assign @ArangoGutierrez
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
LGTM label has been added. Git tree hash: 76881da39702170941dbb7922ead2421d162d726
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ArangoGutierrez, marquiz, tobiasgiese The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -55,11 +56,16 @@ spec: | |||
name: grpc | |||
- containerPort: {{ .Values.master.metricsPort | default "8081" }} | |||
name: metrics | |||
- containerPort: 8082 |
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.
do we need to make this one configurable for the host network case ?
i.e also add cmdline flag since currently AFAIU value is fixed [1]
[1]
GrpcHealthPort = 8082 |
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.
See PR description :)
out-of-scope: will make the health port configurable in a follow-up PR to be able to run all daemonsets in the host's network namespace (i.e., avoid port conflicts)
Will create the PR in the next hour(s)
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.
oh sorry :)
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 be fixed in #1885
We have to run our NFD workers in the host network. Also we need additional env variables such as KUBERNETES_SERVICE_HOST and _PORT. To achieve this we can simply add generic helm values. The default behavior is not changed.
Also exposed all container ports because hostNetwork need this information, see
out-of-scope: will make the health port configurable in a follow-up PR to be able to run all daemonsets in the host's network namespace (i.e., avoid port conflicts)