Secure and efficient installation with KubeOps KOSI
The KubeOps Software Installer is designed to simplify the installation of packages and programs in Kubernetes clusters.
One notable feature: KubeOps KOSI is optimized for BSI-tested environments. Therefore it adheres to strict security standards and ensures a safe and secure installation process.
KubeOps KOSI has a batch engine and a “flow logic” that can be extended by plugins. This enhances the functionality and an easy use.
KubeOps KOSI can package everything into a self-sufficient package, which can then be transported in any complex and secure environment. This package is immutable and ensures that your packages remain secure and stable.
The KOSI definition file as a bundling of all necessary applications.
Successful installation of KOSI and all required container images.
Detailed view after an succesfull installation of the compressed file.
Software Deployment
For software-manufacturers KOSI offers the possibility to release their Kubernetes software as a single self-sufficient deployment file.
To do so, the manifacturer packages all needed deployment artefacts via
kosi build
Via
kosi push
the packages gets uploaded to the KubeOps HUB giving either access only to the specific customer or even to the whole community if desired.
This simplifies the download process for the clients, as they just need to run a
kosi install
to install the packages into their cluster, even behind a proxy (Airgap).
Helm Deployment
For customers planning to deploy a Helmchart KubeOps KOSI gives support at downloading and packaging all needed container images and artefacts into a single, self-sufficient package with
kosi build
By publishing via
kosi push
the package can be downloaded from KubeOps HUB as a single installation fine.
All relevant dependencies are managed by KOSI insuring installation.
Therefore, installing software with KOSI into your cluster simplifies, secures and eases the process of software deployments into your environments.
Deployment without KOSI
Problems:
Manual Processing
Effort Intensive
Vulnerable
Not reproducable
The classic way of software delivery in the cloud cosmos is using helm-charts and container images.
Requiering software manufactureres to publish the helm-chart, uploadcontainer images into a public registry and provide their customers with a list of all requiered artefacts.
Customers then have to pull these images, configure the helm-chart according to the environment specific settings, check all checksums etc. this often even gets more complex in productive environments. As these tend to have an outgoing proxy preventing broad access to the internet.