Operations | Monitoring | ITSM | DevOps | Cloud

Amazon Elastic Kubernetes Service (EKS) is a managed container service designed to deploy and scale cloud-based or on-premise Kubernetes applications. AWS released EKS Blueprints to provide customers with a framework for creating internal development platforms on EKS.

Another post inspired by our weekly internal enablement office hours [should we open this up to the public?] and a few conversations at DevOps Days Atlanta, talking about the experience with Kubernetes can reverberate some sighs. Though in our weekly enablement office hours, the blunt question was asked “well why is Kubernetes so difficult?”. Industry thought leaders would state that Kubernetes is a platform to build other platforms.

The latest version of the Splunk Operator builds upon the release we made last year with a whole host of new features and fixes. We like Kubernetes for Splunk since it allows us to automate away a lot of the Splunk Administrative toil needed to set up and run distributed environments. It also brings a resiliency and ease of scale to our heavy-lifting components like Search Heads and Indexer Clusters.

Containers are great for developers, but containers are also an excellent way to create reproducible, secure, and portable applications. Applications can be deployed reliably and migrated to multiple computing environments quickly using containers. It could be the developer's laptop to the testing environment or staging to the production environment. To use Dockers, Kubernetes, etc., it has been necessary to build containers.

During the past two weeks, our Frontend and Backend teams were busy bees 🐝 with a particular sprint dedicated to bug hunting �� and improvements! Yes, both of the two weeks sprints were dedicated to bugs and improvements ONLY: tracking them, then solving them; gotta catch ‘em all 🚀