Ticq Software Engineering’s Post

Managing Critical System Components with Kubernetes Static Pods A financial services company encountered several challenges while deploying the logging service as a static pod Inconsistent Deployment Across Nodes, , Difficulty in Updating Static Pods Monitoring and Alerting To solve this, I ensure consistent deployment across nodes Audit Node Configurations. Firstly, I conducted a thorough audit of the kubelet configurations across all nodes to ensure that each node was correctly configured to deploy the static pod. The kubelet looks for static pod definitions in a specific directory (e.g., /etc/kubernetes/manifests). So the first step was to make sure that all nodes have the correct manifest files in this directory. Secondly, I created an Ansible playbook to automate the deployment of static pod manifest files across all nodes. This ensured that the correct configuration was applied consistently across the entire cluster. In order to simplify updates, I moved the static pod manifest files into a Kubernetes ConfigMap. This allowed to manage the pod definitions centrally and use a DaemonSet to deploy a small sidecar container on each node, which would watch the ConfigMap for changes and update the static pod manifest on the node accordingly. Moreover, the sidecar container also supported rolling updates, where it would sequentially update the static pod manifest on each node and restart the pod to ensure minimal disruption to the logging service For next steps, keep following posts #kubernetes#Seniordevopsengineer#monitoring and logging#staticpods

Discover the Kubernetes API Gateway: Your centralized access point to services within your cluster. Simplify interactions for external clients, reducing complexity and enhancing efficiency. Explore how it can streamline your Kubernetes experience! #Kubernetes #APIGateway #Efficiency https://lnkd.in/eZNcAR39

Why Kubernetes is removing in-tree cloud-provider integration support in v1.31, and how it can affect you https://lnkd.in/dWdkAFSR

Our Development focus for this week at #NuNet 👀 🛰 p2p remote shell is unreliable 📂 Change all README-DEV into README files 🔗 Kubernetes Integration Scope and Definitions In Review now: ▶️ Isolate tokenomics tests for adding to CI/CD pipeline For more 👉 https://gitlab.com/nunet

Happy to share this blogpost I wrote on multi-cluster service mesh for Red Hat Developer with the support of Jacek Ewertowski. The multi-primary multi-cluster deployment model will be in dev preview in OpenShift Service Mesh 2.6, and generally available in OSSM 3.

Containerization is a technology developed to conveniently transfer a development or production application from one location to another location. It is a bundle of the development environment, source code and even the database. The technology developed to manage the containers is called Kubernetes. Kubernetes (sometimes spelled k8s or "kube") is an open-source container orchestration platform that automates many of the tedious tasks associated with deploying, managing, and growing containerized applications. Sources: Blog Link from CIC https://lnkd.in/gW69vCDn #Kubernetes #k8s #kube #CHGITCONSULTANCY

Develop a script to streamline the process of gathering information on desired operators within OpenShift, saving time and enhancing the efficiency of adding operators to your ImageSetConfiguration configuration file.

It's been a year that I used Gateway API in Kubernetes environment. Although Ingress is considered as Tried-and-Proven, I think we won't wait long before Gateway API becomes the standard way of managing routing in Kubernetes. I mainly used it for everything so far : Ingress, Load Balancing, and even as a Service mesh along with Istio, and I am very satisfied with it. If you are interested about it, you can just read the documentation here : https://lnkd.in/daPbQMFt, it's really easy to understand and to set up. #K8s #GatewayAPI #Service_Mesh

🤝 Meet Tempo Monolithic mode. This mode is ideal for small deployments, demo and test setups, and is the recommended migration path of the Red Hat OpenShift distributed tracing platform (Jaeger) all-in-one deployment. Read on to learn more.

Here's the Blog on Multi-Cluster setup with OpenShift Service Mesh from the "Masters" themself :D https://lnkd.in/d3ESH-Nn