Red Kubes, the creators of Otomi, announces new feature for developers to deploy applications in Kubernetes according to security and compliance policies.

In this article, we’ll explore some of the CI/CD capabilities Otomi has to offer. Note that the setup used in this article is only one of the multiple scenario’s. Otomi supports activating only the required capabilities for your use case in a composable way.

KubeClarity is the latest integrated app to be added to Otomi and can be installed via drag-and-drop to get you running scans in minutes. In this blog, Ryan Dardis, Cloud Native Engineer @ Red Kubes, gives you more on this integration.

In this article, Jehoszafat Zimnowoda, Engineering Manager @ Red Kubes, explains some of the design decisions his team has made for implementing a zero-trust network architecture for Kubernetes.

In this blog post, we’ll explain why you would need developer self-service and how you can get started.

In this blog post we’ll zoom in into a couple of best practices when using Kubernetes in production, and show how these best practices are supported by Otomi.

In a series of 3 posts , we’ll take a look at how Kubernetes fits into the broader technology landscape, and how an enterprise container platform is crucial for digital transformation and the adoption of cloud-native.

In a series of 3 posts , we’ll take a look at how Kubernetes fits into the broader technology landscape, and how an enterprise container platform is crucial for digital transformation and the adoption of cloud-native.

In a series of 3 posts , we’ll take a look at how Kubernetes fits into the broader technology landscape, and how an enterprise container platform is crucial for digital transformation and the adoption of cloud-native.

To implement SRE successfully, there needs to be a correct culture, a collaboration between development and operations (and security), skilled people and of course a good technical architecture. This is where Otomi comes in.

University Professor José van Dijck argues in “De correspondent” today that it is necessary to reduce dependence on big technology companies and develop alternatives with public money.

Getting started with a container platform is a daunting task, and there are many options to choose from, from do-it-yourself (DIY) to fully managed services. Let’s look at the DIY Kubernetes-based platform building approach.

This is our story about building a multi-tenant Kubernetes environment that facilitates various DevOps teams (tenants) with their own Kubernetes namespace and private container registry.

How can you speed up the adoption of Kubernetes? The answer: An internal Kubernetes-based developer platform. Read this blog to learn how

In this post, we’ll explore Kubernetes security risks and challenges you’re likely to encounter, especially in production and at scale, and provide 10 best practices and practical recommendations to help you secure cloud-native infrastructure and applications.

Unfortunately, things aren’t as simple when starting with a container platform. Kubernetes is only one part of a much more complicated infrastructure puzzle, integrating additional software to create an enterprise-grade platform.

This is a story behind the trenches of writing Rego policies and how to unravel the cumbersome process of working with Gatekeeper vs Conftest for validating Kubernetes resources.

You can now use your favorite identity provider to provide SSO and Role-Based Access to Otomi Console, Otomi Apps, and public exposed services.

Improve Kubernetes security by preventing human error and misconfiguration with Otomi Container Platform Container orchestration with Kubernetes is hard enough and securing container and Kubernetes environments brought this to a whole new level of complexity.