TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile
TBC πŸ‡¨πŸ‡²

@tbc_foot

Je parle du Cameroun et de l’Afrique en gΓ©nΓ©ral. Je suis un passionnΓ© du football ⚽️⚽️⚽️

ID: 263656403

calendar_today10-03-2011 13:39:50

617 Tweet

80 Followers

320 Following

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Cloud interview question: In AWS, when you create a new subnet inside a VPC, is it public or private by default? and why? #cloud #aws

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

USA, India, and Nigeria are the top countries engaging with my posts. Looks like these countries dominate tech conversations on X. What about your analytics? 🌍

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Conversation between HR and the CEO: HR: We need to increase staff salaries. If we don’t, they might leave and we’ll lose talent. CEO: But what if we don’t… and they stay? Then we win.

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Quick AWS question: Which statement is wrong? A) Two Availability Zones can be in the same subnet B) Two subnets can be in the same Availability Zone Explain why. #aws #cloud

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Answer: It depends on the VPC. 1 - Default VPC A new subnet will behave public because: - The default route table already has 0.0.0.0/0 β€”>IGW - Instances can receive auto-assigned public IPs 2 - Custom VPC A new subnet will behave private because: - There is no route to an IGW

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Cloud engineers, I need help! I have several public subnets that receive traffic from the internet. I want one subnet to stop receiving internet traffic, without converting it to a private subnet. What would you change? #AWS #CloudComputing #DevOps

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Answer: Statement A is wrong. An Availability Zone is physical infrastructure, a datacenter. A subnet is a virtual network inside a VPC. A subnet belongs to only one AZ, but you can create many subnets in the same AZ.

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Kubernetes Upgrade Tip 5/10 Before upgrading your cluster, do whatever you want but don’t skip this step: verify cluster health. Make sure: - All nodes are Ready - No failing pods - Control plane components are stable Upgrading an unhealthy cluster is like renovating a

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

I spoke with a developer at a large financial company. He told me he’s never even heard of Claude. Some engineers are still doing real work:

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Unpopular opinion If you really master Terraform, you don’t need Terragrunt or Terraform Workspaces to manage multi-environments. A well designed module structure and proper state separation are enough. #terraform #IAC

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

A recruiter calls you about a job. They need someone with strong Ansible and Golang experience. You tell them you’re not familiar with those tools. They ask you to update your resume and add them anyway. Would you do it, or refuse? #Devops

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

Kubernetes Upgrade Tip 6/10 Always prepare a recovery plan before upgrading. Kubernetes does not support downgrades. If something goes wrong, you can’t simply roll back the version. Plan your alternatives: - Restore the cluster from an etcd backup - Recreate the cluster

TBC πŸ‡¨πŸ‡² (@tbc_foot) 's Twitter Profile Photo

I am resting this weekend, so I’ll leave you with this quote: Linus Torvalds created Linux at 21 Colonel Sanders founded KFC at 65 Some people start early Some people start late It is never too late to start