Asking for help? Comment out what you need so we can get more information to help you!
I am trying to create NLB (internal facing) using Ingress. I am using the below manifest file to deploy the ingress. The NLB endpoint has not been created. it’s blank
Is there any pre-requisites such as IAM policies/roles needed.
I have my workloads deployed into AWS EKS cluster
Cluster information:
Kubernetes version: 1.29
Cloud being used: (put bare-metal if not on a public cloud): AWS
Installation method: Manifest (shared below)
Host OS: N/A
CNI and version:
CRI and version:
Kubelet version
v1.29.0-eks-5e0fdde
Worker node: Docker version 24.0.2, build cb74dfc
Worker node: containerd://1.7.11
Worker node: Amazon Linux 2
apiVersion: networking#k8s#io/v1
kind: Ingress
metadata:
name: ingress-service-nlb
namespace: tresleai
annotations:
kubernetes#io/ingress#class: “nlb”
#kubernetes#io/role/internal-elb: 1
service#beta#kubernetes#io/aws-load-balancer-type: “internal”
service#beta#kubernetes#io/aws-load-balancer-internal: “true”
service#beta#kubernetes#io/aws-load-balancer-nlb-target-type: “instance”
service#beta#kubernetes#io/aws-load-balancer-ssl-cert: “arn:aws:acm:us-east-2:XYZ”
service#beta#kubernetes#io/aws-load-balancer-ssl-ports: “443”
service#beta#kubernetes#io/aws-load-balancer-ssl-negotiation-policy: “ELBSecurityPolicy-2016-08”
#nlb#ingress#kubernetes#io/security-groups: “sg-8edf9b29776”
service#beta#kubernetes#io/aws-load-balancer-scheme: “internal”
service#beta#kubernetes#io/aws-load-balancer-backend-protocol: tcp
#nlb#ingress#kubernetes#io/scheme: “internal”
spec:
rules:
- host: service#test#ai
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: test-service
port:
number: 80