Unable to Access 2048 Application via Ingress on AWS EKS Playground

Playgrounds
,
#1

Hi Support Team,

I am currently using the AWS Playground environment and attempting to deploy the sample 2048 application on an EKS cluster using Ingress and exposing the ALB service to the internet.

I am following the steps provided in the following guide:

https://medium.com/@simiao-it/deploying-a-2048-game-on-aws-eks-with-ingress-and-alb-a-step-by-step-guide-6279394749c4

I was able to complete most of the setup successfully. However, when I run the following command:

kubectl get ingress -n game2048

the EXTERNAL-ADDRESS field remains empty, and I am unable to access the application externally.

Could you please confirm whether creating an external Load Balancer (ALB) is permitted in the AWS Playground environment?

If external load balancers are supported, could you please share any documentation, articles, or recommended steps to correctly configure and expose the application?

Thank you for your assistance.

Best regards,

#2

Hi @Pankajarora

You can check the answer here Can I create load balancer and ingress controller in EKS of AWS Cloud Playground . . .

#3

Thanks for your Assistance.

#4

Thanks for your Assistance.

Could you please confirm whether creating an external Load Balancer (ALB) is permitted in the AWS Playground environment?

If external load balancers are supported, could you please share any documentation, articles, or recommended steps to correctly configure and expose the application?

Thank you

#5

I’m fairly sure the answer is no. Perhaps @Alistair_KodeKloud knows different, but he would know for sure.

#7

Hi @Pankajarora

I have now added instructions for deploying the loadbalancer controller directly in the playground, including running the 2048 game.

Follow the cluster build instructions. When you reach the end of the build, there is a link to the LB instructions.

#8

@Alistair_KodeKloud
Thanks for assistance and updating the Steps.
I need one more clarity how we are managing IAM Roles in this example
IAM Roles for Service Accounts (IRSA)
EKS Pod Identities
which one is used to configure it & how it is achieved.
Thanks,
Pankaj Arora

#9

To get around the restrictions on the playground, we have a service control policy (SCP) that restricts the names you can give to IAM resources like roles and policies. We explain this in our Playground FAQ.

The terraform configuration files in the repo Alister directs you to use follow these guidelines. Take a like at the files in the eks directory. The file variables.tf lists the names used for the role and for the policy. You’ll note that the names used follow the guidance from the FAQ.