D.1.2.2 DD Multicluster Deployment Instances Configuration Examples
M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on
Cluster2
CNC Configuration (Manager Cluster)
global:
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster
port: 80
- id: Cluster2
role: Cluster2
ip: 10.xx.xx.xx
port: 80
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Manager Cluster)
global:
cncc-iam:
enabled: true
mcncc-core:
enabled: true
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Manager Deployment
self:
cnccId: Cluster1
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster1
role: Cluster1
scheme: https
fqdn: cncc-acore-ingress-gateway.cncc.svc.occne-12ipcluster
port: 443
- id: Cluster2
role: Cluster2
scheme: https
ip: 10.xx.xx.xx
port: 443
instances:
- id : Cluster1-dd-instance1
type: DD-UI
owner: Cluster1
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster1-dd-instance1
type: DD-API
owner: Cluster1
fqdn: ocnaddbackendrouter.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
Note:
In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its an optional configuration.CNCC Configuration (Agent Cluster)
global:
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi
Sample Configuration for HTTPS enabled deployment
- Scheme should be updated to "https" in mCnccIams and aCnccs
- Https port should be updated in mCnccIams and aCnccs
CNCC Configuration (Agent Cluster)
global:
cncc-iam:
enabled: false
mcncc-core:
enabled: false
acncc-core:
enabled: true
isMultiClusterDeployment: true
# Automatic route generation for CNCC Agent Deployment
self:
cnccId: Cluster2
mCnccIams:
- id: Cluster1
scheme: https
ip: 10.xx.xx.xx
mCnccCores:
- id: Cluster1
aCnccs:
- id: Cluster2
role: Cluster2
instances:
- id : Cluster2-dd-instance1
type: DD-UI
owner: Cluster2
fqdn: ocnaddgui.ocnadd-deploy.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnadd
- id : Cluster2-dd-instance1
type: DD-API
owner: Cluster2
fqdn: ocnaddbackendrouter.ocnadd-deploy2.svc
port: 80
apiPrefix: /occne-12ipcluster/ocnaddapi