Open gandhiano opened 4 years ago
Yes this is because a Route is an OpenShift specific. In k8s you have ingress. Routes are more powerful and have some additional capabilities. OpenShift supports everything k8s does plus has extra extentions/capabilities. You should be able to update the Routes and change them to Ingress in the yaml files. I would create new ones and name them k8s. Then you can pull request that. We havent tested on k8s, there could also be some other things regarding role and permissions that need to be adjusted. If you provide a k8s environment I could possibly help but I dont have one.
After following the instructions for the manual operator setup on a plain k8s and applying the reference
podium.yaml
only the etherpad gets deployed, all other components are missing.The operator logs show that it fails while trying to setup the route (which is openshift specific):