5 Reasons to Add Compatibility Testing To Your Distribution Stack
Compatibility Testing — or testing that your application can be successfully installed on unique combinations of Kubernetes distributions (Openshift, EKS, AKS, GKE, K3s, etc.), versions, and configurations — is a relatively new concept in software distribution. Can you imagine a world where you can be confident that every new customer, and every new release, goes smoothly every time? Compatibility Testing can make that happen.
Step-by-Step Guide: Troubleshooting A Failed Deployment Using the Compatibility Matrix
Recently, Replicated launched the Compatibility Matrix - a new tool for spinning up ephemeral Kubernetes clusters on over 60,000+ combinations of distributions, K8s versions, and configurations. Our own internal support team utilizes the Compatibility Matrix to re-create unique customer environments when debugging issues, and this same process can be followed by any ISV that’s integrated the Compatibility Matrix and Replicated platform to quickly resolve their own customers’ issues. Evans Mungai, Sr. Customer Reliability Engineer at Replicated, walks through this process.
Using Telemetry to Test Your Application Across Customer-Representative Environments
Our Director of Solutions Engineering, Chuck D’Antonio, walks through how to use Replicated’s Instance Insights (telemetry) to set up a GitHub action that tests a vendor’s application across their customer-representative environments. Watch the video or read the transcript to learn more.
How Replicated uses the Compatibility Matrix to continuously test our KOTS installer releases on various K8s distributions and versions
Now with Replicated’s new Compatibility Matrix offering, we are able to confidently test KOTS compatibility, and the new Replicated SDK offering, on OpenShift, EKS, GKE, AKS, and more. KOTS testing continues to benefit with each new distribution and version added.
How to Add Continuous Release Testing to Continuous Integration
Diverse operating systems, hardware configurations, and software dependencies among customers can lead to issues that might hinder adoption and satisfaction; thorough compatibility testing as part of your continuous integration (CI) processes minimizes these risks, fostering user trust and loyalty while reducing post-release support burdens.
Testing Releases in Customer-representative Environments
A common challenge for independent software vendors (ISVs) is that the wild diversity of customer-managed operating environments makes testing their application very complex and time consuming. Replicated's Compatibility Matrix offers a solution.
ISV Testing Strategies for Reliability and Compatibility
ISVs should be able to test a release prior to distributing to end-customers. Tests will cascade from quick and simple tests that can be done at every app code commit, to more time consuming complex tests that are run in preparation for a full customer-facing release.