#1 Global Leader in Data Resilience

Veeam Kasten for Kubernetes Red Hat Operator No Longer Available in Red Hat Operator Hub

KB ID: 4774
Product: Veeam Kasten for Kubernetes
Published: 2025-09-24
Last Modified: 2025-09-24
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When attempting to install or upgrade Veeam Kasten (Enterprise - Term) or Veeam Kasten (Enterprise - PAYGO), the operator is no longer available in the Red Hat Operator Hub.

Cause

With the deprecation of the Red Hat Operator Marketplace in April 2025, Kasten licenses can no longer be purchased via the Red Hat Operator Marketplace. As a result, the Enterprise - Term/PAYGO offers have been deprecated from the Red Hat Operator Hub.

Customers currently using either the kasten-k10-operator-paygo-rhmp-bundle or kasten-k10-operator-term-rhmp-bundle will need to transition to the remaining Veeam Kasten operator (k10-kasten-operator-rhmp) and apply the license to it.

Solution

The no longer available Veeam Kasten operator (Enterprise - Term or PAYGO) can safely be deleted and replaced with the remaining available Veeam Kasten operator, while preserving the Kasten instance itself.

  1. Export the k10-config map as a backup.
  2. Ensure Kasten Disaster Recovery is configured, and you have recorded the cluster ID and DR passphrase. This allows you to recover Kasten and its persistent data should something not work as planned during the Operator replacement operation.
  3. Uninstall the OpenShift Veeam Kasten Enterprise Term/Paygo Operator, while leaving the k10 operand and all resources in the kasten-io namespace intact.
    1. Via the OpenShift UI, navigate to Operators > Installed Operators > Veeam Kasten ≡ menu > Uninstall Operator
    2. Ensure that the option "Delete all operand instances for this operator" is unselected.
Red Hat OpenShift console showing the "Installed Operators" page. The Veeam Kasten (Free) operator is listed in the "kasten-io" namespace with status "Succeeded." The "Uninstall Operator" option is highlighted in the actions menu.
Click to enlarge.
Uninstall Operator dialog box asking to uninstall the Veeam Kasten (Free) operator from the "kasten-io" namespace, with an option to delete all operand instances for this operator unselected and "Uninstall" highlighted.
Ensure that the option "Delete all operand instances for this operator" is unselected.
  1. Install the new Veeam Kasten Operator from the Operator Hub.
  2. Confirm the k10 operand is visible in the Veeam Kasten Operator menu.

Note that the single Veeam Kasten operator is fully featured, and there will be no reduction in features, capabilities, or functionality when an enterprise license is applied.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.