Open-source, warehouse-first Customer Data Pipeline and Segment-alternative. Collects and routes clickstream data and builds your customer data lake on your data warehouse.
MIT License
62
stars
48
forks
source link
updated ingress template and values to work with GKE http load balancer #31
These changes to the helm chart were needed to get it working for us on GKE.
This PR changes the service from type LoadBalancer to NodePort and enables the kubernetes Ingress. It also specifies the correct google annotations to use a reserved static IP and prevent the ingress from creating an NEG (Network Endpoint Group). This will cause google to create an "External HTTP load balancer" instead of using TCP. You can then optionally connect an https-target-proxy, forwarding rule on 443 and a google managed cert to support SSL/TLS.
Type of change
[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Related issues
Addresses issue [#20]()
Checklists
Development
[x] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[ ] All tests related to the changed code pass in development
Code review
[x] This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers mentioned in a comment
[ ] Changes have been reviewed by at least one other engineer
[ ] Issue from task tracker has a link to this pull request
Description of the change
These changes to the helm chart were needed to get it working for us on GKE.
This PR changes the service from type
LoadBalancertoNodePortand enables the kubernetes Ingress. It also specifies the correct google annotations to use a reserved static IP and prevent the ingress from creating an NEG (Network Endpoint Group). This will cause google to create an "External HTTP load balancer" instead of using TCP. You can then optionally connect an https-target-proxy, forwarding rule on 443 and a google managed cert to support SSL/TLS.Type of change
Related issues
Checklists
Development
Code review