OpenShift Configuration Platform

One customer came to us with the order to build an OpenShift platform that works independently of direct Internet access (“AirGapped”). OpenShift is a container platform developed by Redhat based on Kubernetes, which is particularly impressive due to its extensive additional functionality, integrability in companies and operational security.

Configurationplatform for OpenShift

When setting up OpenShift, integration into a company is a key part of the task. This is independent of the type of OpenShift installation (bare metal, in the cloud, etc.). In the case of an AirGapped installation, additional steps must also be taken during configuration in order to obtain an executable and updatable OpenShift environment.

Rapid Application Development is a software development principle to use pre-given and frequently needed components of a software application to accelerate the software development process massively. These components are for example functions for user authentication and authorization, user management (self-registration of a user, deactivating an account) but also application designs. With the usage of pre-given component, a lot of development tasks are omitted what rapidly accelerates the software development.

YOTRON put these development principles one step ahead and uses a Kubernetes-ready Rapid Application Development framework. The Kubernetes deployment is an integrated part of the software development, means the software we provide for you is Kubernetes-Ready out-of-the-box.

IONOS SE as part of United Internet Group has the approach to anchoring their own services provided by IONOS more deeply in the company. One aspect of that approach is the usage of their own Cloud provider “IONOS Cloud”. YOTRON supports the BI/BigData-department in the usage of the Cloud for their services.

YOTRON supports DevOps, Cloud and Kubernetes

Goal of the usage of Kubernetes and IONOS Cloud is the seamless integration into the IONOS network. All BI/BigData-applications running in the Cloud shall be reachable in the usual manner. We support IONOS to reach that goal successfully.

• Setup S3-Bucket

• Create a local Helm Repo

  • Package all of your Helm projects locally

  • Indexing of the Helm repository locally

• Deploy the Helm packages

• Add your Repo

(This table of content was done with Markdownmenu)

I want to show how you can use an ordinary S3-Bucket of AWS as a qualified Helm Repository. This is a cheap alternative and is completely serverless.

This Helm Repo is not a fully functional Helm Repository like the Chartmuseum. Means, some management functions of Helm are not supported with an S3-Bucket. For example, you cannot helm push to add Packages to the Bucket, because S3 does not allow pushing files or change files via api calls Helm is using. But for the customer which does not provide own Helm packages is the Repo fully functional.