From 31d17e15791b869b1f9b8827790ed902b1a50bed Mon Sep 17 00:00:00 2001 From: Maxim Rychkov <81160491+Yam1x@users.noreply.github.com> Date: Tue, 16 Dec 2025 14:27:18 +0500 Subject: [PATCH 1/2] docs: change VM resources definition in 2025 first migration between clouds --- cloud/2025-first-migration-between-clouds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloud/2025-first-migration-between-clouds.md b/cloud/2025-first-migration-between-clouds.md index d27983b..0b83395 100644 --- a/cloud/2025-first-migration-between-clouds.md +++ b/cloud/2025-first-migration-between-clouds.md @@ -21,7 +21,7 @@ ## Roadmap -1. Create inner-circle-cloud with 1 VM (2 CPU 10% (the lowest possible) and static IP-address, 8GB RAM) in it using home-cloud as an example. Setup resources in the target cloud using it (local run, no CI/CD) +1. Create inner-circle-cloud with 1 VM (2 CPU 5% (the lowest possible) and static IP-address, 4GB RAM) in it using home-cloud as an example. Setup resources in the target cloud using it (local run, no CI/CD) 1. Create inner-circle-env with prod environment in it that contains: ingress, cert-manager, From 0497220b8ff31f013eb812e0381f403bd1e29f11 Mon Sep 17 00:00:00 2001 From: Maxim Rychkov <81160491+Yam1x@users.noreply.github.com> Date: Sat, 20 Dec 2025 14:59:35 +0500 Subject: [PATCH 2/2] docs: change the way of storing the KUBECONFIG in the runner --- cloud/2025-first-migration-between-clouds.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cloud/2025-first-migration-between-clouds.md b/cloud/2025-first-migration-between-clouds.md index 0b83395..3a6558e 100644 --- a/cloud/2025-first-migration-between-clouds.md +++ b/cloud/2025-first-migration-between-clouds.md @@ -29,9 +29,9 @@ metric-server, 1. Deploy inner-circle-env with its prod environment to the new cluster (local run, no CI/CD) 1. Add needed DNS records for the new Inner Circle Prod domain (new one) **!!! At this point it should show requests to ingress in its logs and LetsEncrypt https certificates are issued** -1. Spin up Intranet GitHub Actions self-hosted runners for IC deployment and prod e2e tests only. They will have cluster's KUBECONFIG in their environment. +1. Spin up Intranet GitHub Actions self-hosted runners for IC deployment and prod e2e tests only. They will have cluster's KUBECONFIG stored in the filesystem. 1. Add a prod deployment workflow to inner-circle-env that will use the new self-hosted runners to deploy it to the new prod on a master branch push. -**!!! At this point we have tested the deployment from the self-hosted runners that contain KUBECONFIG secret in their environment.** +**!!! At this point we have tested the deployment from the self-hosted runners that contain KUBECONFIG in their filesystem.** 1. Migrate inner-circle-employees-api workflows and all its Secrets to inner-circle-items-api. 1. Migrate inner-circle-employees-ui workflows and all its Secrets to inner-circle-time-ui. 1. Freeze any changes to inner-circle-employees-api and inner-circle-employees-ui.