KubeOps Migration

Find out what you need to consider when migrating and which steps are required if you use KubeOps tools.
Tags:

  2 minute read  

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 created your account before March 2025, you must complete the migration steps. Most of the steps will be carried out by us, but some actions are required from your side:

IMPORTANT: These steps are only necessary if you want to use KubeOps 1.7+ tools and have no effect on versions below 1.7.

  • Every user who created an account before March 2025 must choose a new password due to a change in our login process. On your next login attempt, you will be required to set a new password.

  • If you want to use KubeOps tools, you must log in to the kubeops-registry first. A step-by-step guide is available here.

  • We have created new hub and registry spaces. Therefore, you must upload your existing packages to your new private space. The public hub is no longer available. If you encounter any issues while migrating your packages to the new hub, contact us via e-mail for technical support. Existing permissions will be migrated to the new system.

IMPORTANT: The old and new systems are not synchronized. If you want to keep packages in sync across both systems, you must upload them to both.