KubeOpsDoku – kubeops

Kosi: About KubeOps Licences

Mon, 01 Jan 0001 00:00:00 +0000

About KubeOps Licences

For KubeOps 1.7+ licences are required. KubeOps is a tool set which consists of 3 tools: KOSI, KubeOps Platform (Compliance and Compliance + VM). In the table you can see which functions are accessable with given licence.

If you create an account, you get a free 10 days trail-version of our licences.

KubeOps KOSI

Functions	KOSI-Essential	KOSI-Enterprise
Push Packages	✓	✓
Pull Packages	✓	✓
List Packages	✓	✓
Install Packages	✓	✓
Update Packages	✓	✓
Delete Packages	✓	✓
Remove Packages	✓	✓
Encrypt Value-files	✓	✓
Lint Packages	✓	✓
Use Private Registry-space	✓	✓
Use Private Hub	✓	✓
Build *Basic Packages	✓	✓
Build **Advanced Packages	✗	✓
Price	FREE	Contact Sales

* Basic Packages: Package-build-process is limited by the basic plugins. Click Here

Advanced Packages: Package-build-process hase full access to all plugins. Click Here**

KubeOps Platform

Functions	Compliance	Compliance + VM
Cluster Lifecycle Management	✓	✓
- Build Cluster	✓	✓
- Build Airgap Cluster	✓	✓
Security Hardening	✓	✓
Cloud Native VM Hypervisor	✗	✓
Price	Contact Sales	Contact Sales

Kosi: KubeOps Migration

Mon, 01 Jan 0001 00:00:00 +0000

About KubeOps Migration

For KubeOps 1.7+ licences are required. KubeOps is a tool set which consists of 3 tools: KOSI, KubeOps Platform (Compliance and Compliance + VM). Since 1.7 the background process is diffrent then in the older versions. To use your account in the future you have to do some steps to migrate your account.

KubeOps Account

If you had created your account before March 2025 you have to do the steps of the migration. The most of the steps will be done from us but some steps have to be done by you:

IMPORTANT: These steps are only necessary if you want to use tools of the KubeOps 1.7+ and does not have any effect on Versions below 1.7.

Every user before march 2025 has to choose a new password, due to a change in our login process. On your next login attempt you will be forced to choose a new password.
If you want to use the KubeOps tools you have to login into the kubeops-registry first. A guide will help you Here.
We created new hub and registry spaces, so you have to upload you old packages into your brand new private space. The public hub is no longer available. If you have problems with migrating your packages to the new hub send us an E-Mail for technical support and we will help you. Existing permissions will be migrated to the new system.

IMPORTANT: Both systems are not synced so you have to do uploads on both if you want them hold in sync.

Kubeopsctl-2.0: How to migrate from nginx to traefik ingress

Mon, 01 Jan 0001 00:00:00 +0000

Installation

Kubeops supports deploying Traefik as a dynamic ingress controller and reverse proxy. This guide describes a concise, safe migration from an existing nginx-ingress controller to Traefik and explains how to install Traefik and replace a deprecated nginx-ingress deployment. The migration from nginx to Traefik is straightforward; the steps below show the process in order.

Prerequisites

A running Kubernetes cluster with an existing nginx-ingress controller.

1.Create Values file

values.yaml files are required for the Traefik installation:

# values.yaml
packages:
- name: traefik
  enabled: true
  values:
    standard:
      namespace: traefik
      externalIPs: []
    advanced: {}

Note: Update external IPs and other values as per user requirement.

2.Install Traefik

Once the values.yaml files have been created, install Traefik:

# get your desired version/s
kosi search --hub kubeops --ps traefik
# install traefik
kosi install --hub kubeops kubeops/traefik:<desired_version> -f values.yaml --dname traefik

Example

kosi install --hub kubeops kubeops kubeops/traefik:2.1.0_Beta0 -f values.yaml --dname traefik

3.Verify Deployment

Check pods and services in the traefik namespace:

kubectl get pods -n traefik
kubectl get svc -n traefik

Note: Default NodePorts (e.g. 31080 / 31443) might not be reachable. If the default ports are not accessible, determine the ports used by ingress-nginx (e.g. 30080 / 30443) and update Traefik to use the same ports.

4.Remove old nginx-ingress deployment and service

# get version of installed nginx-ingress and its deployment name (--dname)
kosi list
# delete old nginx-ingress
kosi delete --hub kubeops kubeops/ingress-nginx:<installed_version> -f enterprise-values.yaml --dname <kosi_deployment_name>

Edit Traefik service

If nginx used specific NodePorts and you require those same ports, edit the Traefik Service:

kubectl edit svc traefik -n traefik

Update the ports:

Update the ports to match the previous nginx NodePorts if required.

ports:
- name: web
  nodePort: 30080
  port: 80
  targetPort: web
- name: websecure
  nodePort: 30443
  port: 443
  targetPort: websecure

Verify Port Change

kubectl get svc -n traefik

Note: Ensure the nginx Service is removed or its NodePorts are freed before reusing those NodePorts on the Traefik Service.

KubeOpsDoku – kubeops

Kosi: About KubeOps Licences

About KubeOps Licences

KubeOps KOSI

* Basic Packages: Package-build-process is limited by the basic plugins. Click Here

** Advanced Packages: Package-build-process hase full access to all plugins. Click Here

KubeOps Platform

Kosi: KubeOps Migration

About KubeOps Migration

KubeOps Account

Kubeopsctl-2.0: How to migrate from nginx to traefik ingress

Installation

Prerequisites

1.Create Values file

2.Install Traefik

3.Verify Deployment

4.Remove old nginx-ingress deployment and service

Edit Traefik service

Update the ports:

Verify Port Change

Advanced Packages: Package-build-process hase full access to all plugins. Click Here**