You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We are considering to deploy our solution to an Openshift cluster. SycllaDB is an element within our backend system.
We'd like to better understand whether ScyllaDB is OCP certified (https://catalog.redhat.com/platform/red-hat-openstack/software/search) or not.
In other words, is OCP a supported platform for ScyllaDB deployments.
To Reproduce
Steps to reproduce the behavior:
Install ScyllaDB as a container to an OpenShift Cluster (4.8 / 4.10) with a restricted security context
Expected behavior
ScyllaDB container should be up and running.
In other words, is OCP a supported platform for ScyllaDB deployments.
OCP isn't supported yet. At this point, we support (and test) only EKS and GKE.
That said, the operator is written to work on any Kubernetes platform. The difference with OCP is that it's likely gonna need some extra permissions for the more fine-grained levels used by that platform. Maybe some of the tips in #424 will help you get it off the ground. Hopefully, we'll get some cycles to support OpenShift soon.
Describe the bug
We are considering to deploy our solution to an Openshift cluster. SycllaDB is an element within our backend system.
We'd like to better understand whether ScyllaDB is OCP certified (https://catalog.redhat.com/platform/red-hat-openstack/software/search) or not.
In other words, is OCP a supported platform for ScyllaDB deployments.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ScyllaDB container should be up and running.
Config Files
N/A
Logs
N/A
Environment:
Additional context
N/A
The text was updated successfully, but these errors were encountered: