Hi,

Some background about me. I’ve been working on web APIs for the last 5 
years. Initially it started with a monolith codebase, plugging in all sorts 
of APIs and packaging it all together. It was fairly easy to setup a 
staging cluster due to the simplicity involved in hosting the code and 
configurations. 

Over the years I’ve realised the importance of services and have adopted 
that strategy over time. With multiple micro services comes the problem of 
discovery, config management and tooling around it so we created ansible 
playbooks with configurations for 3 main environments. However we were 
still hosting these services the old school way of running it directly on 
VMs. A few major problems arise due to this.

- There are 3 pre-defined environments. prod, stage and test. To create an 
environment, lets say for individual developers, a lot of manual work is 
involved.
- Infrastructure cost increases linearly with every new environment we 
spawn.
- Service discovery, config management becomes a mess.

A few months ago after reading about kubernetes and how it solves most of 
these problems, I’ve created pods for most of our services (mostly using 
brute-force), this is just a start and I’ve made notes of all technical 
debts which have been accumulated during this process. The immediate 
consumers of this platform is the QA team. Long term plans also involve 
replaying production traffic on this cluster and to bench it out.


My questions:

1. How is the staging cluster setup in your organisation?
2. What are some of the learnings and the problems faced while building it?
3. Is the thought process of having a working cluster for every developer 
make sense?

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to