Skip to content
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

[FEAT #6416] nodePort value can be set now #6417

Merged
merged 7 commits into from
Mar 6, 2024
Merged

[FEAT #6416] nodePort value can be set now #6417

merged 7 commits into from
Mar 6, 2024

Conversation

ryayon
Copy link
Contributor

@ryayon ryayon commented Feb 21, 2024

PR Description

Allow to set a port when the service is NodePort type

Which issue(s) this PR fixes

Fixes #6416

Notes to the Reviewer

PR Checklist

  • CHANGELOG.md updated
  • Documentation added

@CLAassistant
Copy link

CLAassistant commented Feb 21, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@tpaschalis tpaschalis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there @ryayon! Apologies for the delayed reply here!

I think this does make sense as a PR. I'm still on the fence on if we should provide a random-ish default like you did here, or default to an empty value that preserves the previous behavior (but also allow setting it).

In the meantime, could you please fix the linting error about the README file, and also possibly add a test?

@ryayon
Copy link
Contributor Author

ryayon commented Mar 1, 2024

Hey there @ryayon! Apologies for the delayed reply here!

I think this does make sense as a PR. I'm still on the fence on if we should provide a random-ish default like you did here, or default to an empty value that preserves the previous behavior (but also allow setting it).

In the meantime, could you please fix the linting error about the README file, and also possibly add a test?

No worries.
Thank you for your feedback and let me know for the default port value.
In the meantime, I fixed the README (although I am not sure what was the issue) and I created a specific test.

@tpaschalis
Copy link
Member

cc @ryayon sorry for the hassle here; I've fixed a merge conflict (so you might have to pull first), but can you run make generate-helm-tests to also regenerate the test folders?

cc @captncraig in case he has any strong opinions here, but I think that it'd be best if we let the default value empty and just set it if the user provided a non-default value instead.

@ryayon
Copy link
Contributor Author

ryayon commented Mar 6, 2024

No need to feel sorry @tpaschalis .
Thank you for your help and time.
I just pushed a new commit with the test folders regenerated.
In addition, I pulled all previous commits as suggested.
Let me know for any issue.

@@ -254,6 +254,8 @@ service:
enabled: true
# -- Service type
type: ClusterIP
# -- NodePort port
nodePort: 31128
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps the comment could indicate this only takes effect when type is NodePort.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Absolutely.
I just fixed it.

@captncraig
Copy link
Contributor

The ci wants you to run make generate-helm-docs.

@ryayon
Copy link
Contributor Author

ryayon commented Mar 6, 2024

The ci wants you to run make generate-helm-docs.

Done

@captncraig captncraig merged commit 5fb5395 into grafana:main Mar 6, 2024
10 checks passed
@ryayon ryayon deleted the feat-6416-nodeport branch March 8, 2024 11:11
@github-actions github-actions bot added the frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed. label Apr 8, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Locked due to a period of inactivity. Please open new issues or PRs if more discussion is needed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possibility to set the value of NodePort with the Helm Chart
4 participants