A solution to create QA ephemeral  environment in Kubernetes

1. qainit
Matteo Madeddu, Lorenzo Mancuso, Prima Assicurazioni - 2022
a solution to create QA ephemeral
environment in Kubernetes

2. A new feature is coming
Mark starts writing code…

3. Feature ready!
…and eventually close the task 👏👏👏

4. Feature ready!
How can he test it properly?

5. Test phase
Docker?

6. Test phase
docker-compose?

8. qainit in a nutshell

9. qainit step 1
Mark authenticate with an internal custom cli to auth0

10. qainit step 1
Then, it asks qainit to create a new environment

11. qainit step 2
This is where magic happens

12. qainit step 2
First, qainit call Github
An internal dependency resolution starts from the speci
f
ic
microservice requested to collect all other microservices needed

13. qainit step 2
Second, qainit call Kubernetes api
An ephemeral namespace is created to host all required microservices:
common resources (databases, metrics collector, etc) are deployed inside it

14. Qainit use DroneCI Api to promote speci
f
ic build of all microservices requested:
the CI/CD completes the deployment in k8s cluster using helm and a common chart
qainit step 3

15. A tool called external-dns provide the CNAME records for each microservice that
needs it inside a dedicated zone inside Cloud
f
lare
qa created

16. What about the solution?
• qainit is written in Elixir, leverages Commanded and adopt CQRS
paradigm to keep tracks of the status of resources (qa namespaces,
microservices, etc)
Some more details

17. What about the solution?
• qainit is written in Elixir, leverages Commanded and adopt CQRS
paradigm to keep tracks of the status of resources (qa namespaces,
microservices, etc)
• the qa created use statefull sets and AWS speci
f
ic drivers (network and
volumes plugins) to preserve data across days
Some more details

18. What about the solution?
• qainit is written in Elixir, leverages Commanded and adopt CQRS
paradigm to keep tracks of the status of resources (qa namespaces,
microservices, etc)
• the qa created use statefull sets and AWS speci
f
ic drivers (network and
volumes plugins) to preserve data across days
• the solution is fully scalable - thus, qa are frozen each day by scaling to
zero the replicas, and can be defrost by developers using our custom cli,
providing almost zero costs
Some more details

19. A new feature is coming…
qainit is ready!

20. A new feature is coming…
qainit is ready!
Made with love by Prima’s Platform Engineers

21. Q1: How do you test your environment?
This is the way we do it

22. Q2: Is there someone with a similar environment?
This is the way we do it

23. Q3: Would you be interested in a solution like
the one we use?
This is the way we do it

24. Q&A