okta-azure-kubernetes-cosmosdb-example VS kdash

Kubernetes Microservices on Azure with Cosmos DB

git clone https://github.com/oktadev/okta-azure-kubernetes-cosmosdb-example.git \ azure-k8s-cosmosdb cd azure-k8s-cosmosdb git fetch --all --tags git checkout tags/start -b working

A temporary fix taken from the issue on GitHub is to override the health reporting implementation so that it returns DOWN instead of OUT_OF_SERVICE while the program is still starting. This blocks it from ever reporting OUT_OF_SERVICE. You can see the fix in the EurekaFix.java file in the store app.

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.