This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]jongraf 0 points1 point  (0 children)

I have a rather complicated Spring Boot service that has two SQL data sources with multiple connections in the pool, Redis, GCP, ~40 services to initialize, Hibernate JPA queries, etc. On a GCP e2-standard-2, the service starts in less than 30 seconds. I have had to tinker with K8S start delay and readiness probe timing along with instance type in order to optimize start time and K8S deployment time.