Skip to content

docs: change VM resources definition in 2025 first migration between clouds and change the way of the KUBECONFIG storing #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Yam1x wants to merge 2 commits into
base: 2025-first-migration-between-clouds
Choose a base branch
from
Open

docs: change VM resources definition in 2025 first migration between clouds and change the way of the KUBECONFIG storing #401

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
31d17e1
docs: change VM resources definition in 2025 first migration between …
Yam1x Dec 16, 2025
0497220
docs: change the way of storing the KUBECONFIG in the runner
Yam1x Dec 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions cloud/2025-first-migration-between-clouds.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,17 +21,17 @@

## 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,
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.
Expand Down