Cluster Specific Changes
- Support internal container registries for the RabbitMQ cluster operator
- Fix compatibility issue with CronJob for Kubernetes version v1.20 or earlier
More information on upgrading KOTS can be found here.
These changes are not related to the GuardRails platform functionality, but add improvements and fixes to the GuardRails on-premise deployment in terms of resiliency, high availability, as well as some minor fixes.
Note: This will create a new RabbitMQ cluster and the messages that are in the queue will not be migrated. There may be hanging scan jobs that will be cleaned up automatically within 24 hours. Any stuck scans can also be restarted in the dashboard.