Skip to content

Terrakube on GKE exposed with GCP Loadbalancer #388

Answered by alfespa17
jmorenog asked this question in Q&A
Discussion options

You must be logged in to vote

Hello @jmorenog there was an issue about that sometime ago, maybe you can check here:

AzBuilder/terrakube-helm-chart#61

I think you need to use something like this when deploying the helm chart values, the service type should be NodePort and use the gke ingress annotations

## API properties
api:
  serviceType: "NodePort"

## Executor properties
executor:
  serviceType: "NodePort"

## Registry properties
registry:
  serviceType: "NodePort"

## Registry properties
registry:
  serviceType: "NodePort"

## Ingress properties
ingress:
  useTls: true
  includeTlsHosts: false
  ui:
    enabled: true
    domain: "terrakube-ui.minikube.net"
    path: "/"
    pathType: "ImplementationSpecific" 
    a…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by jcanizalez
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants