Closed jjacob7734 closed 3 months ago
Status:
Unity-Venue-Dev
SDAP config to deploy ingress-nginx
componentingress-nginx
pod deploys but the associated Application Load Balancer (ALB) gets stuck in pending
state for external IP assignment Failed build model due to unable to resolve at least one subnet
. I am currently researching possible solutions to this. I did not have this problem in the SDAP deployment I did in the Unity-Dev
account last year.Status:
ingress-nginx
load balancer deployment issue by adding tags to the subnets in unity-venue-dev
:
Public subnets:
kubernetes.io/role/elb: 1
kubernetes.io/cluster/unity-as-venuedev-sdap: shared
Private subnets:
kubernetes.io/role/internal-elb: 1
kubernetes.io/cluster/unity-as-venuedev-sdap: shared
ingress-nginx
pod is now deployed, but I think I need to add a Kubernetes Node Selector to ensure it gets deployed to the same host where the SDAP nexus-webapp
pod is running. Those 2 pods are currently running on different hosts and I suspect that is causing the load balancer target group to not be entirely healthy.ingress-nginx
pod to run on the sdap-driver
node where the SDAP nexus-webapp
pod is running.@jjacob7734 ping for status.
Status:
ingress-nginx
pod is now deployed successfully on the sdap-driver
node where the SDAP nexus-webapp
pod is running.ingress-nginx
service is running and healthy.
@jjacob7734 ping for status. Per the plan this was supposed to be complete in 24.2.1.