Let’s say that you’ve successfully scaled your application infrastructure. You’re using DevOps for rapid and collaborative software development, and underlying application infrastructure scales to meet current demand via container orchestration like Kubernetes or HashiCorp Nomad. Writing and deploying new code is going great…until it isn’t–until the application configuration or other components have drifted from alignment, or until a radical need for refactoring becomes present, with no easy way to recreate an environment, or when a rollback to previous state becomes a sink or swim moment, etc. Automating  declarative  infrastructure deployment and configuration not only makes it easier to quickly ship code with stunning new features and improvements, but also alleviates the conflicts of drift, and maintains control of the  state  of the deployment environment. Whereas cloud-native applications are built to run in fluid and dynamic cloud environments, this is where GitOps really shines.…