-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Described installation process not working #2100
Comments
Although the documentation implies that node ports are automatically created, they are not. Nodeports is probably also not how you want to expose your service. You typically expose services in OpenShift via routes, but it looks like the You can create the following route instead (it creates a route on HTTPS): kind: Route
apiVersion: route.openshift.io/v1
metadata:
name: minio
namespace: minio-operator
labels:
app.kubernetes.io/instance: minio-operator
app.kubernetes.io/name: operator
name: console
olm.managed: 'true'
operators.coreos.com/minio-operator.minio-operator: ''
spec:
host: operator-console-route-minio-operator.apps-crc.testing
port:
targetPort: https
to:
kind: Service
name: console
tls:
termination: passthrough
insecureEdgeTerminationPolicy: Redirect You can then go to https://operator-console-route-minio-operator.apps-crc.testing and the console should open. You may get errors about invalid certificates, because the certificate won't be valid for your hostname. We'll revise the documentation for OpenShift deployment. We made some changes and they aren't reflected here yet. I'll also look into the issue why the http port redirects back to https. |
The The TLS redirection forwards to the same hostname/port, but with the When deploying via the standard Helm script, the @pjuarezd Is there a reason why the OpenShift deployment deploys with cluster certficates when deploying via the OpenShift console? @dvaldivia The TLS redirection functionality doesn't make much sense if the host header contains an explicit port. We may want to remove that redirect in those cases and return an error instead. |
@ravindk89 we need to do some updates in the docs for Openshift installs |
I am following the installation procedure for the operator as described here on my local CRC version 4.15.3 as welll as on a productive system running on 4.13.37
https://min.io/docs/minio/kubernetes/openshift/operations/installation.html
First issue is that the Operator is installed without any Nodeport
This is the spec of the Route that i created according to your documentation. All I get is Applicatin not available even if all pods are running
The text was updated successfully, but these errors were encountered: