36 lines
1.7 KiB
YAML
36 lines
1.7 KiB
YAML
|
components:
|
||
|
|
# -- First, we switch the default SharePoint OFF
|
||
|
|
sharepoint: false
|
||
|
|
|
||
|
|
# -- Then we enable two sharepoint instances to be used with different configurations
|
||
|
|
sharepointa: true
|
||
|
|
sharepointb: true
|
||
|
|
|
||
|
|
sharepointa:
|
||
|
|
clusterService:
|
||
|
|
# -- This enabled the cluster service
|
||
|
|
enabled: true
|
||
|
|
# -- the cluster Ingress needs to know the context path it should react on.
|
||
|
|
contextPath: "/nscale_spc"
|
||
|
|
ingress:
|
||
|
|
# -- we turn off the original ingress as the common context path would block the deployment
|
||
|
|
enabled: false
|
||
|
|
# -- The default contextPath for sharepointa is `nscale_spca` to make sure we have distinguishable paths for all sharepoint instances.
|
||
|
|
# however, in this case we re-use the service as cluster service and die ingress as cluster ingress, so we switch to the general
|
||
|
|
# contextPath, as if it was a single component deployment
|
||
|
|
contextPath: "/nscale_spc"
|
||
|
|
sharepointb:
|
||
|
|
clusterService:
|
||
|
|
# -- on the second SharePoint Instance, we **disable** the cluster service, as it is already created by sharepointa.
|
||
|
|
enabled: false
|
||
|
|
# -- however, we need to set the context path, as this tells the networkPolicy to open up for ingress even though we switch die Ingress off in the
|
||
|
|
# next step
|
||
|
|
contextPath: "/nscale_spc"
|
||
|
|
ingress:
|
||
|
|
# -- we turn off the original ingress as the common context path would block the deployment
|
||
|
|
enabled: false
|
||
|
|
# -- The default contextPath for sharepointb is `nscale_spcb` to make sure we have distinguishable paths for all sharepoint instances.
|
||
|
|
# however, in this case we re-use the service as cluster service and die ingress as cluster ingress, so we switch to the general
|
||
|
|
# contextPath, as if it was a single component deployment
|
||
|
|
contextPath: "/nscale_spc"
|