jx boot on EKS: No external IP assigned to ingress

Created on 6 May 2020 · 7Comments · Source: jenkins-x/jx

Summary

I created a new JX cluster using the terraform template and following all the documentation on EKS, I cannot access the cluster as the ingress is never assigned an IP (and load balancer is never created.

Expected behavior

Loadbalancer created and external IP assigned.

Actual behavior

No external IP

Jx version

NAME VERSION
jx 2.1.23
Kubernetes cluster v1.15.11-eks-af3caf
kubectl v1.13.2
helm client 2.16.5
git 2.17.0
Operating System Mac OS X 10.15.4 build 19E287

Kubernetes cluster

EKS

Operating system / Environment

MacOS

Terraform Params:

module "eks-jx" {
  source = "jenkins-x/eks-jx/aws"

  vault_user             = "jenkins"
  apex_domain            = <external domain>
  cluster_name           = <name>
  desired_node_count     = 3
  enable_external_dns    = true
  enable_tls             = true
  max_node_count         = 5
  min_node_count         = 3
  node_machine_type      = "c4.xlarge"
  production_letsencrypt = true
  region                 = "eu-central-1"
  tls_email              = <email>

}

JX Requirements (Storage and vault removed)

autoUpdate:
  enabled: false
  schedule: ""
terraform: true
cluster:
  clusterName: <name>
  environmentGitOwner: ""
  provider: eks
  region: "eu-central-1"
gitops: true
environments:
  - key: dev
  - key: staging
  - key: production
ingress:
  domain: <domain>
  ignoreLoadBalancer: true
  externalDNS: true
  tls:
    email: <email>
    enabled: true
    production: true
kaniko: true

areeks areterraform kinbug prioritcritical

Source

kne-ci

All 7 comments

If anyone has any insight or workarounds for this it would be a massive help and it's a blocker for me.

kne-ci on 7 May 2020

FYI @hferentschik, for follow-up.

deanesmith on 7 May 2020

@kne-ci Are u seeing that the external IP is in a pending state after you do a jx boot? If you have never provisioned any ELBs on your AWS account, then you need to create a load balancer outside of EKS, tear it down, and then retry jx boot. I hit a similar issue (not exactly the same issue as urs), and this helped.
Source: https://kubernetes.slack.com/archives/C9MBGQJRH/p1563207693144300