rosibes

DevOps Engineer - learning things I find cool

[rosibes @rosibes27]

As I said 4 month ago, "Wait for the USDT dominance to consolidate around 6.3 - 6.7 %".

Take a look at the first picture and thank me later :P

[rosibes @rosibes27]

Told y’all two months ago, “sell all your altcoins when USD D taps the pink zone.”

Anyways, still not the best time to buy. Wait for the Usdt dominance to consolidate around 6.3 - 6.7%.

[rosibes @rosibes27]

@sauravstwt book

[rosibes @rosibes27]

Security is a MUST!
Ever wondered how Keycloak works? Take a look at the picture below.

[rosibes @rosibes27]

Deploying applications on Kubernetes doesn't have to be complicated. Enter Helm! ⚓️

Helm streamlines packaging, deploying, and managing even the most complex applications with its templating power. Essential for consistent, repeatable deployments.

[rosibes @rosibes27]

RAM vs CPU - you've heard of them, but do you truly understand their roles?

Take a look at the representation below.

[rosibes @rosibes27]

Azure VPN Gateway vs. ExpressRoute: Which hybrid connection wins? 🥊

[rosibes @rosibes27]

If your production latency depends on the public internet, you're living on the edge. 🛑

Switch from VPN Gateway to Azure ExpressRoute for a private, dedicated 'highway' to the cloud. Lower latency, better security, more peace of mind. 🚀 #CloudInfrastructure #Azure104 #Azure

[rosibes @rosibes27]

If your production latency depends on the public internet, you're living on the edge. 🛑

Switch from VPN Gateway to Azure ExpressRoute for a private, dedicated 'highway' to the cloud. Lower latency, better security, more peace of mind. 🚀 #CloudInfrastructure #Azure104 #Azure

[rosibes @rosibes27]

Azure Advisor: Your personalized guide to Azure best practices. 🛠️

Do you actually understand its role in your stack? Let’s break it down.

[rosibes @rosibes27]

Stop guessing how permissions inherit in the cloud. Here is a visual breakdown of Azure RBAC hierarchy. 🚀 #Azure #CloudSecurity

[rosibes @rosibes27]

You have 2 Azure VNets. Each has a VPN Gateway costing $130+/mo.

To cut costs, you peer them and enable 'Gateway Transit' on the Hub.

But the Spoke still can’t reach on-prem.

What setting must be toggled on the Spoke peering to use the Hub’s Gateway?

[rosibes @rosibes27]

SMB (Server Message Block) protocol breakdown 👇

A tree is just a shared resource (folder or printer).
The client selects the share, the server responds with a Tree ID, and communication begins.
Access depends on assigned permissions.

[rosibes @rosibes27]

@BowTiedCyber Default Gateway

[rosibes @rosibes27]

We’ve all heard about TCP, but do you really know what happens under the hood?
Check out the illustration below

[rosibes @rosibes27]

@JeremysITLab b) Since the /29 subnet has a block size of 8 addresses, the last octet increments by 8. The IP address 172.28.109.230 falls within the subnet range, where 172.28.109.224 is the network address. So, the first usable address is 172.28.109.225, which is used as the default gateway.

[rosibes @rosibes27]

@TheCyberPatron_ nmap

[rosibes @rosibes27]

@BowTiedCyber ACL explicitly permits or denies traffic. So you would configure it to Permit TCP 443 and Deny all else

[rosibes @rosibes27]

@EvyTechno C). ls -p | grep -v /

[rosibes @rosibes27]

@brankopetric00 No, the code is not gone.
The git branch is just a reference to a commit. So the command ‘git branch -D..’ deletes the branch reference named ‘feature/login’, not the actual commit.

We can use ‘git reflog’ to find the lost commits.

[rosibes @rosibes27]

Kubernetes schedules based on declared CPU requests

Not real CPU usage

CPU is effectively reserved on paper

[Branko @brankopetric00]

A Pod is stuck in 'Pending' state.

`kubectl describe pod` events:
- 0/5 nodes are available
- 3 Insufficient cpu
- 2 node(s) had taint {https://t.co/h9y6PiaqBi: }, that the pod didn't tolerate

You check the 3 worker nodes. They have 50% CPU allocatable remaining.

Why does the scheduler think they have insufficient CPU?

[rosibes @rosibes27]

@brankopetric00

[rosibes @rosibes27]

@brankopetric00 Pods have over-requested CPU and Kubernetes schedules on promised CPU, not used CPU.