Application requirements
If your application is intended to run on the SUSE Rancher Prime platform, it will need to be validated as SUSE Ready for Rancher. To do this, you will need to demonstrate that:
- your organization is the primary developer or maintainer of the software
- you have tested the software on the latest supported version of RKE2 or K3s managed by SUSE Rancher
- you provide commercial support for the software on the declared SUSE Rancher and RKE2 or K3s versions and configurations
- you publish documentation specifying the supported versions of SUSE Rancher and RKE2 or K3s for the software
- you actively maintain and proactively update the software so that:
- critical vulnerabilities are patched in a timely way
- release notes disclose serious bugs or vulnerabilities
- you publish a license and/or terms & conditions for the software
- your software does not compete commercially with SUSE Rancher Prime, SUSE Edge, or SUSE AI
For Kubernetes CSI drivers, the following specific behaviors should be tested:
- the driver deploys and functions in a Rancher-managed Kubernetes cluster
- persistent Volumes (PVs) and Persistent Volume Claims (PVCs) can be created, attached, and deleted successfully
- snapshots (if supported) work as expected.
- Storage features exposed in the Rancher UI work with the driver (e.g. Storage > PersistentVolumeClaim > Create)
For Software-as-a-Service (SaaS) platforms that integrate with Rancher but do not run as workloads on Rancher-managed Kubernetes, certification is based on testing the integration point(s). You will need to demonstrate that:
- the integration is documented, making clear what support you provide for the integration
- you periodically test the combined functionality using the relevant software interfaces (e.g., APIs, software agents) to ensure that the integration works as documented