-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Helm: Ability to change loki-read and loki-write services to NodePort #9077
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.
[docs team] LGTM
@@ -143,3 +143,5 @@ If you would like to add your organization to the list, please open a PR to add | |||
## License | |||
|
|||
Grafana Loki is distributed under [AGPL-3.0-only](LICENSE). For Apache-2.0 exceptions, see [LICENSING.md](LICENSING.md). | |||
|
|||
# changes |
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.
This entry should not be here. Changes should be added to the CHANGELOG
@karlkeppner1 Can you add a HELM changelog entry and update the Helm chart version to 5.5.8? An example can be found here. |
What this PR does / why we need it:
When deployed to AWS EKS, services must be of type
NodePort
ifingressClassName: alb
. By adding the ability to specify service type for the loki-read and loki-write services, EKS users can now use the chart without loki-gateway. Added ability to specify aclusterIP
if servicetype: ClusterIP
. Added ability to specify annotations for each service.Which issue(s) this PR fixes:
I never raised an issue for this. I needed it personally, so I wrote it.
Special notes for your reviewer:
Previous defaults were added explicitly in values.yaml to maintain backwards compatibility.