dianaarnos opened a new pull request #7997:
URL: https://github.com/apache/pinot/pull/7997


   ## 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: https://github.com/apache/pinot/issues/7996
   
   Sample result  `helm template pinot` when Ingress is enabled:
   ```bash
   # Source: pinot/templates/broker/ingress.yaml
   apiVersion: extensions/v1beta1
   kind: Ingress
   metadata:
     name: pinot-broker
     labels:
       helm.sh/chart: pinot-0.2.6-SNAPSHOT
       app: pinot
       chart: pinot-0.2.6-SNAPSHOT
       release: pinot
       app.kubernetes.io/version: "0.2.5-SNAPSHOT"
       app.kubernetes.io/managed-by: Helm
       heritage: Helm
       component: broker
   spec:
     rules:
     - host: localhost
       http:
         paths:
           - path: /
             backend:
               serviceName: pinot-broker
               servicePort: 8099
   ---
   # Source: pinot/templates/controller/ingress.yaml
   apiVersion: extensions/v1beta1
   kind: Ingress
   metadata:
     name: pinot-controller
     labels:
       helm.sh/chart: pinot-0.2.6-SNAPSHOT
       app: pinot
       chart: pinot-0.2.6-SNAPSHOT
       release: pinot
       app.kubernetes.io/version: "0.2.5-SNAPSHOT"
       app.kubernetes.io/managed-by: Helm
       heritage: Helm
       component: controller
   spec:
     rules:
       - host: localhost
         http:
           paths:
             - path: /
               backend:
                 serviceName: pinot-controller
                 servicePort: 9000
   ```
   ## Upgrade Notes
   Does this PR prevent a zero down-time upgrade? (Assume upgrade order: 
Controller, Broker, Server, Minion)
   * [ ] Yes (Please label as **<code>backward-incompat</code>**, and complete 
the section below on Release Notes)
   
   Does this PR fix a zero-downtime upgrade introduced earlier?
   * [ ] Yes (Please label this as **<code>backward-incompat</code>**, and 
complete the section below on Release Notes)
   
   Does this PR otherwise need attention when creating release notes? Things to 
consider:
   - New configuration options
   - Deprecation of configurations
   - Signature changes to public methods/interfaces
   - New plugins added or old plugins removed
   * [x] Yes (Please label this PR as **<code>release-notes</code>** and 
complete the section on Release Notes)
   ## Release Notes
   WIP
   <!-- If you have tagged this as either backward-incompat or release-notes,
   you MUST add text here that you would like to see appear in release notes of 
the
   next release. -->
   
   <!-- If you have a series of commits adding or enabling a feature, then
   add this section only in final commit that marks the feature completed.
   Refer to earlier release notes to see examples of text.
   -->
   ## Documentation
   WIP
   <!-- If you have introduced a new feature or configuration, please add it to 
the documentation as well.
   See 
https://docs.pinot.apache.org/developers/developers-and-contributors/update-document
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to