AWS-based deployment

Help Developers
1

Hi all,

I know there’s been a couple of discussions about deploying to AWS services, which I’ve been referencing heavily while trying to translate the DigitalOcean deployment guide to AWS services, but I’m still having an issue with the getting an external IP address for the nginx ingress controller.

kubectl get service -n ingress-nginx

returns the following:

ingress-nginx-controller             LoadBalancer   10.100.32.50    <pending>     80:31012/TCP,443:30886/TCP   5h42m
ingress-nginx-controller-admission   ClusterIP      10.100.170.72   <none>        443/TCP                      5h42m


Working through the discussion in this post, Speckle Certificate Errors in NGINX Ingress Controller, I’m having an issue when trying to get to the path for:

cm-acme-http-solver-XXXX
(I’m replacing the randomly generated string with XXXX for this post).


I can see cm-acme… as an ingress resource using:

kubectl get ingress --namespace speckle

but getting the path using:

kubectl describe cm-acme-http-solver-XXXX --namespace speckle

returns

error: the server doesn't have a resource type "cm-acme-http-solver-XXXX"

Relevant section of above post: Speckle Certificate Errors in NGINX Ingress Controller - #4 by iainsproat

Here are the AWS services I’m using:

  1. Cluster on EKS
  2. Postgres on RDS
  3. Redis in Elasticache
  4. S3 bucket

Would love any thoughts on debugging!

2

The kubectl describe command should have the resource name prefixed with the resource type, e.g.:

kubectl describe ingress/cm-acme-http-solver-XXXX --namespace speckle

(NB, I’m guessing the resource type here, haven’t had a chance to test the above)

And regarding the pending loadbalancer, the nginx ingress is attempting to connect with the underlying AWS infrastructure to create the necessary loadbalancer resource. I’d suggest describing the service/ingress-nginx-controller in kubernetes, or viewing the latest kubernetes events. They may have messages which could give some pointers.

You may also want to do an internet search, as it seems many others have similar issues regarding creating loadbalancers from nginx in AWS.

Hope this helps,

Iain