okta-jhipster-k8s-eks-microservices-example VS kdash

You need a microservice stack to deploy to the cluster. I'm using a microservice stack scaffolded for demo purposes using JHipster. You can use another microservice stack if you want. If you prefer using the same application as in this demo, then you can either scaffold it using JHipster JDL or clone the sample repository from GitHub.

A simple terminal dashboard for Kubernetes built with Rust, best alternative k9s

kdash: A fast and simple dashboard for Kubernetes. Its created by me :)

[Optional] KDash

Note: I'm using KDash to monitor the cluster; you can try it or use kubectl, k9s, and so on as you prefer.

When you communicate with a Kubernetes cluster, using kubectl, or a client library, or a tool like KDash, you are primarily interacting with the Kubernetes API server. The API server is responsible for managing the cluster and is responsible for handling requests from a client.

Mostly KDash and if possible progress on a JHipster blueprint for Rust microservices

I'm not building web-apps yet, currently i'm doing a terminal UI app. You can check the cargo.toml for deps. I'm planning to build a Rust blueprint for JHipster quite soon so I'll be able to directly compare productivity with Spring boot. And yes there is no equivalent of SB in Rust but I don't think you need that in Rust, there are great web frameworks like Actix or Rocket which provides most of what you need from SB and since you dont have to do OOP in Rust you actually dont need many Hibernate like features IMO, but you have http://diesel.rs/ to cover that.