GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 28 · 12 min readOpenShift application Day-2: 7 guardrails that refuse the bad state in GitThe problem that troubleshooting does not solve Part 2 delivered a runbook of ten commands. The team knows how to diagnose a CrashLoop, how to tell a 503 from a 502 on the Route, and that oc logs --pr00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 27 · 12 min readApplication troubleshooting on OpenShift: 10 commands before blaming the clusterThe problem that the first wrong command amplifies The API Route stops responding at 2 PM on a Wednesday. The incident reaches the team channel and the first reflex is oc get nodes. The nodes are Read00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 26 · 13 min readOpenShift Application Day-2: 7 Mistakes That Take Down the Service, Not the ClusterThe first oc apply in the namespace usually passes. The Route responds, the pod reaches Running, and the pipeline turns green. Everything works — until the Route certificate expires with no warning, t00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 21 · 8 min readKafka on OpenShift in 15 Minutes: From Zero to Cluster with Red Hat Streams for Apache KafkaYou need a Kafka cluster on OpenShift. Apache Kafka's documentation has dozens of pages on broker configuration, startup scripts, and environment variables. Before producing your first message, two ho00
GFGuilherme Ferreiraingferreir.hashnode.dev·Aug 21 · 11 min readKafka for High Availability in Practice: Patterns with Red Hat Streams for Apache KafkaIt was 2:23 PM on a Friday when the alert came in: the order processing service had stopped consuming messages. The Kafka broker in the secondary datacenter had failed, taking down every partition who00
