Operations | Monitoring | ITSM | DevOps | Cloud

In this blog post, I will be looking at 10 best practices for Kubernetes security policy design. Application modernization is a strategic initiative that changes the way enterprises are doing business. The journey requires a significant investment in people, processes, and technology in order to achieve the desired business outcomes of accelerating the pace of innovation, optimizing cost, and improving an enterprise’s overall security posture.

Current observability practice is largely based on manual instrumentation, which requires adding code in relevant points in the user’s business logic code to generate telemetry data. This can become quite burdensome and create a barrier to entry for many wishing to implement observability in their environment. This is especially true in Kubernetes environments and microservices architecture.

Ever since Google made Kubernetes open-source in 2014, it has enjoyed incredible growth, helping businesses of all sizes to successfully manage their containers and ultimately make the most of all that our cloud native world has to offer. Individual users certainly initially led the charge with Kubernetes, identifying issues, and generally exploring the best ways to intelligently test, manage, and deploy workloads.

A couple of days ago, I was pleasantly surprised to suddenly see a tweet come in from Viktor Farcic. Viktor now works at upbound.io who developed Crossplane, and he also runs his own popular YouTube channel and co-hosts DevOps Paradox podcast. He’s well respected in the cloud native community. When I saw the tweet and noticed that Viktor had recorded a review of Civo on YouTube, I was just hoping he was kind to us...and I am pleased to say he was!

I am super excited to announce that we released the support of Environment Variables and Secrets. Watch the video to see those features in action. Environment Variables and Secrets are similar. The main difference is that the Secrets are encrypted and the value can’t be revealed. Both are injected at the build and runtime of your applications. Give it a try now! Resources: I am eager to have your feedback. Put a comment here. ‍

The growing adoption of microservices and Kubernetes gave rise to the need to efficiently manage, schedule, and control Kubernetes clusters, where tools like Terraform are helping many organizations address those challenges today. Terraform is a popular choice among DevOps and Platform Engineering teams as engineers can use the tool to quickly spin up and edit environments directly from their CI/CD pipelines.