If you are on Shipa Cloud today, some of you might have noticed a new module called Insights. We are pleased to announce the soft launch / initial release of Shipa Insights and certainly have a lot in store as we continue to build out the module. As more items continue to shift left towards the developer and the rise of the full lifecycle developer continues to occur, outside of technical non-functional requirements such as connectivity, reporting and metrics are also important. From a DevOps and platform engineering perspective, how do you report on engineering efficiency and conformance/compliance? Now with Shipa Insights, you can answer and report on these questions/concerns almost immediately.
Securing K8s Applications at Scale, with Shipa Insights:
Legacy Kubernetes Workloads – It’s Bound To Happen
Sounding like an oxymoron, but legacy Kubernetes workloads will eventually be in your organization. Software certainly ages like milk not like wine, at some point the original engineers for the workload would leave the product/project. Legacy projects in the SDLC phase tend to wind down and not have lots of active development going on.
With Kubernetes, these workloads can survive for a while. Redeploying a workload to a Kubernetes cluster can be achieved without the original engineers who wrote the feature. In your organization, there might be workloads like this already on Kubernetes; deep intrinsic knowledge is gone.
Having a clear picture of what is running across the organization and how well the applications have aged in terms of security and compliance posture is the goal of many DevOps and platform engineering teams. Now with Shipa Insights, this is possible for workloads either deployed or not deployed by Shipa.
Scaling The Truth – Shipa Insights
Managing one Kubernetes cluster is simple enough. One can interrogate each of the workloads that are running. As you start to increase the number of clusters past a singular cluster, for example in our virtual cluster post, having detailed knowledge of what and how items are running is challenging. The number of workloads can increase significantly and the engineering expertise for each workload can be varying as workloads and teams mature.
Running native kubectl commands can be information overload. Today with Shipa Insights, you are able to validate workloads against your defined Shipa Policies.
Your workloads can either be deployed through Shipa e.g a Shipa Application or auto-discovered through Shipa. This is substantial because the auto-discovered portion of Shipa Insights allows you to get a lay of the land very quickly and provide coverage to all of your Kubernetes workloads with no interruption. As we start to build out the module and continuously add features. Shipa Insights will become a hub for not only policy violations but engineering efficiency insights.
Just Getting Started – Shipa Insights
We are just getting started with Shipa Insights. The goal of Shipa Insights is to provide a clear view of workload compliance/conformance and engineering efficiency stats such as the DORA Metrics. Make sure to stay tuned to what we are building as functionality will continuously be released.
-The Entire Shipa Team