Kubernetes and operators

One major issue with GitOps, as the DevOps team was experiencing, is that the platform that the application relies on is the main execution engine for the GitOps process. Although the execution in the underlying platform being inherent is helpful, it also means that the execution is like a black box where the underlying actions are relatively hidden.

To avoid this black box issue with the GitOps process, the DevOps team decided to dive deeper into what Argo CD is doing during an execution event. By documenting Argo CD's underlying tasks, the troubleshooting process will become much simpler. The first step to understand and document is how Kubernetes behaves when an execution command is triggered.

Up to this point, the teams are basically just running helm commands. The team will monitor the helm output for a success or failure message, and then moves on. What the DevOps team wanted to understand was how Kubernetes behaved when the command was run...