Skip to content

updated ingress template and values to work with GKE http load balancer - #31

Open
immber wants to merge 1 commit into
rudderlabs:masterfrom
coralproject:GKE-ingress
Open

updated ingress template and values to work with GKE http load balancer#31
immber wants to merge 1 commit into
rudderlabs:masterfrom
coralproject:GKE-ingress

Conversation

@immber

@immber immber commented Jun 29, 2021

Copy link
Copy Markdown

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 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

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

Addresses issue #20

Checklists

Development

  • 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

  • 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

Comment thread Chart.yaml
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 0.2.0
version: 0.2.1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this is a breaking change to existing functionality and defaults, so it's more than a patch version bump.

Comment thread values.yaml
controlPlaneJSON: false
ingress:
enabled: false
enabled: true

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

i don't think defaulting to a GKE specific ingress enabled is the right choice here, although i agree that it should be supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants