Kubernetes Support from Philippines
I am a Kubernetes expert from Philippines. My job is to help support enterprise Kubernetes Cluster to run at optimal performance, monitor the workload, and keep the lights on. I bring Kubernetes support to the next level in the enterprise that I work with by introducing GitOps. The idea behind GitOps is to have Git as the single source of truth for my Kubernetes Cluster resources and other configuration. This enable me to reduce the disparity of Kubernetes environment which is a typical problem of organizations.
Kubernetes Monitoring
Kubernetes is self-healing infrastructure. Yet it doesn't mean an enterprise can leave it unmonitored. Errors at application level happen like CrashLoopBack error, and certificates do expires causing apps unresponsive. A Kubernetes monitoring must be in placed as simple as opensource Prometheus and Grafana, or SysDig for those that has budget. Onboarding apps to observability is not a simple tasks either. Requires agent installation and adding few code snippets to an already running application.
Kubernetes Maintenance
The most difficult part of Kubernetes upgrade is when an enterprise is lagging behind 5 versions with shared critical application running in a cluster. Thus a a proper upgrade strategy such as blue-green Kubernetes upgrade where a new up to date cluster is built and apps from the old cluster are moved then a cutover takes place. Once verified functional the latest version(blue) takes over the old cluster(green).
Kubernetes Release Support
It may seem simple that Kubernetes deployment in operation is easy but it becomes difficult once we talk of having to support multiple business units with many applications, and environment. What seems to be a simple kubectl apply -f deployment.yaml becomes complicated and cumbersome if we factor in production support at night and weekend. Human error do happen, and fatigue takes place. That is why automating the deployment to Kubernetes is essential to support the frequent releases of enterprise. My expertise is properly deploy changes to Kubernetes cluster smooth and easy.
Kubernetes GitOps
The biggest problem of Kubernetes support is the disparity of the infrastructure and configuration drift causing error and rework. Human makes mistake due to manual configuration. My approach of Kubernetes support is through GitOps. A single source of truth in the form of YAML or HELM are stored in GitHub repository representing the entire Kubernetes cluster resources. Any changes are done through code and is track by version control. The moment a change happen, these updates through code are synced to different Kubernetes environment automatically. As a result; environment disparity is prevented with less manual intervention.
