-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add Ingress to Broker and Controller helm charts #7997
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
Conversation
|
cc @WyriHaximus |
b027ef0 to
66e8684
Compare
|
@dianaarnos let us know when its ready for review |
66e8684 to
deac519
Compare
|
cc: @xiangfu0 |
Codecov Report
@@ Coverage Diff @@
## master #7997 +/- ##
============================================
- Coverage 71.30% 64.87% -6.43%
- Complexity 4214 4224 +10
============================================
Files 1596 1554 -42
Lines 82756 81088 -1668
Branches 12348 12173 -175
============================================
- Hits 59006 52608 -6398
- Misses 19761 24730 +4969
+ Partials 3989 3750 -239
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
deac519 to
94f4cf5
Compare
|
Hi @xiangfu0, do you have any updates regarding this PR? 🙂 |
Overall lgtm, just wanna change the enable flag name for future update, others are fine. |
What would you prefer us to change it to @xiangfu0? EDIT: You want to put the version in it correct? (Refs: https://github.com/apache/pinot/pull/7997/files#r794328610 ) |
This enables Ingress out of the box for anyone using Helm to deploy Pinot to Kubernetes. All one need to do is override the default values inside the values.yaml file.
94f4cf5 to
e80cae9
Compare
xiangfu0
left a comment
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! Thanks for your contribution!
This enables Ingress out of the box for anyone using Helm to deploy Pinot to Kubernetes. All one need to do is override the default values inside the values.yaml file.
|
@xiangfu0 @dianaarnos based on the template of ingress and documentation it wont work. in documentation is below template file is using syntax like |
Description
This enables Ingress out of the box for anyone using Helm to deploy Pinot to Kubernetes.
All one need to do is override the default values inside the values.yaml file.
Ingress is disabled as default.
Important: One needs to be running Kubernetes that supports
apiVersion: extensions/v1beta1.Related issue: #7996
Sample result
helm template pinotwhen Ingress is enabled:Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)
backward-incompat, and complete the section below on Release Notes)Does this PR fix a zero-downtime upgrade introduced earlier?
backward-incompat, and complete the section below on Release Notes)Does this PR otherwise need attention when creating release notes? Things to consider:
release-notesand complete the section on Release Notes)Release Notes
Now it is possible to enable an Ingress resource for the Broker and the Controller through the helm chart by setting it as
enabledand adding the necessary configurations.