Skip to content

Commit ca5943f

Browse files
renedamyonsj-porter-knime
authored andcommitted
Updated 1.18 docs for Openshift and other fixes
1 parent f5f8f6e commit ca5943f

12 files changed

Lines changed: 157 additions & 304 deletions

File tree

README.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -74,14 +74,12 @@ Additionally, a TLS cert will need to be provisioned either directly or via addi
7474

7575
If creating the cert explicitly, it's typically recommended to create a cert with the common name hub.example.com, and listing all domains above as subject alternative names, or using a wildcard for the subject alternative name (i.e. *.hub.example.com)
7676

77-
## Ingress Rules
77+
## Openshift Ingress Rules
7878

79-
`Ingress` rules will need to be manually created prior to install. A working template of the required `Ingresses` can be found under [/networking/ingress-nginx/ingress.yaml](https://bitbucket.org/KNIME/knime-business-hub-public/src/main/networking/ingress-nginx/ingress.yaml).
79+
`Ingress` rules will need to be manually created prior to install for Openshift clusters. A working template of the required `Ingress` can be found under [/networking/openshift/ingress.yaml](https://github.com/knime/knime-business-hub-public/tree/main/networking/ingress-nginx/ingress.yaml).
8080

8181
Ingress rules may need to be further updated depending on use of other tools to correctly set DNS, TLS, etc.
8282

83-
See "Deploy Ingress Resources in `networking/ingress-nginx` for more information.
84-
8583
## Install KNIME Business Hub
8684

8785
Once the following supplemental steps above have been completed, the admin should be able to proceed with the remainder of the install as documented at docs.knime.com

networking/ingress-nginx/README.md

Lines changed: 0 additions & 91 deletions
This file was deleted.

networking/ingress-nginx/ingress.yaml

Lines changed: 0 additions & 168 deletions
This file was deleted.

networking/istio/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ By default the deployment includes an Istio Gateway that uses the correct DNS na
4343

4444
Istio can be installed manually into an Openshift cluster or setup using the Openshift Service Mesh Operator.
4545

46-
> See [Openshift Docs: Service Mesh](https://docs.openshift.com/container-platform/latest/service_mesh/v2x/ossm-about.html) for information on setting up the Service Mesh and [/networking/istio/openshift-servicemesh](https://bitbucket.org/KNIME/knime-business-hub-public/src/main/networking/istio/openshift-servicemesh) for recommended configuration options.
46+
> See [Openshift Docs: Service Mesh](https://docs.openshift.com/container-platform/latest/service_mesh/v2x/ossm-about.html) for information on setting up the Service Mesh and [/networking/openshift](https://github.com/knime/knime-business-hub-public/tree/main/networking/istio/openshift-servicemesh) for recommended configuration options.
4747
4848
When installing on Openshift manually use the following command.
4949

networking/istio/istio-config.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ spec:
3131
enabled: true
3232
## Root for docker image paths e.g. "gcr.io/istio-release". Using gcr.io since dockerhub introduced stricter rate limits.
3333
hub: "gcr.io/istio-release"
34-
## Version tag for docker images e.g. "1.24.2".
34+
## Version tag for docker images e.g. "1.28.3".
3535
tag: "1.28.3"
3636
meshConfig:
3737
accessLogFile: /dev/stdout

networking/istio/openshift-servicemesh/README.md

Lines changed: 0 additions & 37 deletions
This file was deleted.

0 commit comments

Comments
 (0)