Guide to setting up multiple SSH configurations for git operations

It’s the last week of the year, which means more time to clean up those tech debts…

It all started with this alert…

What are processes? A process is basically a program in execution and a program is a piece of code which may be a single line or millions of lines long written in a programming language. When a UNIX machine gets powered up, the kernel will be loaded and complete its initialization process. Once initialization is completed, the kernel creates a set of processes in the user space, including the scheduling of the system management daemon process (usually named init) which has PID 1 and is responsible for running the right complement of services and daemons at any given time.

I manage multiple EKS clusters (multi-envs multi-tenants) at work and access to these is via Bastion instances deployed within each VPC of those clusters. However this approach can become unmaintainable over time as the number of Bastion instances will grow with the number of clusters we manage. This means additional effort required for monitoring and maintenance of each of those Bastion instances. This led to the idea of removing all Bastion instances and configure direct access to Apiservers instead.