Hello. This is Akiyama from Azure Cloud Solution Architect. This time, I will continue to write about the story of migrating to k8s at our Mamoru Biz.

• Vol.1 Deciding to Migrate from App Service to AKS
• Vol.2 AKS(k8s) Preparations <- 本記事
• Vol.3 AKS(k8s) 移行

Vol.2 AKS(k8s) 移行の下準備

for Migration In the previous article, we decided to migrate. The next step is to secure resources and explain to your team to get started with the migration.

Resource Acquisition

As I wrote in the previous article, infrastructure engineers are concurrent. To manage the Azure layer on its own, k8s, we needed a member who could implement the DevOps layer. For this project, I decided to work with Jaeho, who works in the DevOps area.

For projects like AKS(k8s) migration, having a DevOps environment is a must. Even though it is your own SaaS business, there is not much difference between doing it and imitating a contract business. Reference: Serverless/Container Implementation Support |

I decided on a rough sense of cost, scope, and schedule and started moving. The technical part will be discussed in a later article.

Instructions to the Team

The explanation to the team was done step by step, gradually. Roughly speaking, it is the following four steps.

Before the project starts

• Infrastructure members (explanation and solicitation to the project)
• Core members of the Business Leader and Application Engineer (clarification and consensus building)

Project in progress

• Application Engineer (facilitating explanation and preparation)
• The whole team (description)

The explanation (persuasion) materials for each member are as written in the previous article. Since Mamoru Biz has a decent number of people actively involved, we explained it to the entire team at the end of the migration project.

In English.

This is because nearly half of the 15-20 people mentioned above are not Japanese. Meetings and chats are held in English on a daily basis. It is natural that this briefing session is also in English. This was my first English presentation in my life.

Below is a part of the script from that time.

I wanted to put in a script that was a little less serious, and I said, "Developers will get paid more (with the introduction of k8s)!" and I have a good memory that no one was snorting. (Maybe it's because it's remote)

Conclusion

So far, I have written about preparing for the transition and rooting. Next time, I'll finally write about the technical part of the migration.