diff --git a/README.md b/README.md index 3200e2bcb..91466f3d6 100644 --- a/README.md +++ b/README.md @@ -178,7 +178,7 @@ docker build -t //console-operator: . # following: docker.io/openshift/origin-console-operator:latest # for development, you are going to push to an alternate registry. # specifically it can look something like this: -docker build -t quay.io/benjaminapetersen/console-operator:latest . +docker build -f Dockerfile.rhel7 -t quay.io/benjaminapetersen/console-operator:latest . ``` You can optionally build a specific version. diff --git a/bindata/assets/services/console-nodeport-service.yaml b/bindata/assets/services/console-nodeport-service.yaml new file mode 100644 index 000000000..6a2f0eb0a --- /dev/null +++ b/bindata/assets/services/console-nodeport-service.yaml @@ -0,0 +1,20 @@ +# This 'console' service manifest is used when the ingress cluster capability is disabled. +# Service will be exposed using a NodePort to enable the alternative ingress. +apiVersion: v1 +kind: Service +metadata: + name: console + namespace: openshift-console + labels: + app: console +spec: + ports: + - name: https + protocol: TCP + port: 443 + targetPort: 8443 + selector: + app: console + component: ui + type: NodePort + sessionAffinity: None diff --git a/bindata/assets/services/downloads-nodeport-service.yaml b/bindata/assets/services/downloads-nodeport-service.yaml new file mode 100644 index 000000000..4f9046072 --- /dev/null +++ b/bindata/assets/services/downloads-nodeport-service.yaml @@ -0,0 +1,18 @@ +# This 'downloads' service manifest is used when the ingress cluster capability is disabled. +# Service will be exposed using a NodePort to enable the alternative ingress. +apiVersion: v1 +kind: Service +metadata: + namespace: openshift-console + name: downloads +spec: + ports: + - name: http + port: 80 + protocol: TCP + targetPort: 8080 + selector: + app: console + component: downloads + type: NodePort + sessionAffinity: None diff --git a/docs/alb-ingress-rosa-hcp.md b/docs/alb-ingress-rosa-hcp.md new file mode 100644 index 000000000..ce8b19307 --- /dev/null +++ b/docs/alb-ingress-rosa-hcp.md @@ -0,0 +1,115 @@ +# Use AWS ALB as alternative ingress on ROSA HCP + +This doc aims at showing the effort needed to expose the OpenShift console via AWS ALB on a ROSA HCP cluster. +The use case in mind is [HyperShift hosted clusters where the Ingress capability is disabled](https://github.com/openshift/enhancements/pull/1415). + +## Requirements + +- ROSA HCP OpenShift cluster. +- [AWS Load Balancer Operator installed and its controller created](https://docs.openshift.com/rosa/networking/aws-load-balancer-operator.html). +- User logged as a cluster admin. + +## Procedure + +### Create certificate in AWS Certificate Manager + +In order to configure an HTTPS listener on AWS ALB you need to have a certificate created in AWS Certificate Manager. +You can import an existing certificate or request a new one. Make sure the certificate is created in the same region as your cluster. +Note the certificate ARN, you will need it later. + +### Create Ingress resources for the NodePort services + +To provision ALBs create the following resources: +```bash +cat <