K8s may not be the best option for every project, but my original point was that choosing it ought not blow out the budget or delivery window of a project. Maybe, you might shave a week or two off a greenfield project by going with something like Elastic Beanstalk, but in the scheme of things that's a rounding error.
To put things in perspective, a typical deployment for a small app requires 3-4 short configuration files specific to K8s plus your Docker container.
Furthermore, you'd generally still use the cloud managed services like Elastic Cache and RDS when developing K8s applications. I was merely using a Postgres as an example in my mini-not-quite-a-tutorial before.
So yeah, if Elastic Beanstalk is working for you and you think the tradeoff between flexibility and simplicity is right for your project, then keep doing what you're doing.
I'm not sure how familiar you are with AWS, EKS, Kubernetes, or Docker in general and I don't know of a guide that encompasses all these technologies.
My best advice would be:
1) Get a little toy Docker container running locally with a http server that responds with "Hello world"
2) Try and deploy it to as a pod to a local Kubernetes cluster (Docker desktop has one built in or you can try deploying Minikube if you're feeling adventurous)
3) Add an ingress and service to your cluster, so you can access your server from a browser
4) Expand your cluster by installing something like Postgres on it and have your toy app query it and print out a query result in response to requests
5) Try passing your toy app the password to login to Postgres as a Kubernetes Secret via an environmental variable
6) Start exploring EKS specific deployment documentation such as the links below.
7) Start learning about helm
https://docs.aws.amazon.com/eks/latest/userguide/create-clus...
https://docs.aws.amazon.com/eks/latest/userguide/sample-depl...
https://learn.hashicorp.com/tutorials/terraform/eks (Once your comfortable with everything else)