1. Cloud Native Core Console Installation and Upgrade Guide
  2. CNC Console Instances Configuration Examples

CNC Console Instances Configuration Examples

The following section lists the CNC Console instances configuration examples for single cluster and multi cluster deployment of supported NFs.

Note:

In the following examples, mCnccIams port is assumed as "80". The mCnccIams port configuration must be added only if port is other than "80".

BSF Instances Configuration Examples

BSF Single Cluster Deployment Instance Configuration Examples

CNCC Configuration


global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local      
      port: 80   
  instances:
    - id : Cluster1-bsf-instance1
      type: BSF
      owner: Cluster1
      fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local 
      port: 80

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


global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443   
  instances:
    - id : Cluster1-bsf-instance1
      type: BSF
      owner: Cluster1
      fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local  
      port: 80

BSF Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1     
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80 
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id : Cluster1-bsf-instance1
      type: BSF
      owner: Cluster1
      fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local  
      port: 80
    - id : Cluster2-bsf-instance1
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local  
      port: 80
    - id : Cluster2-bsf-instance2
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local  
      port: 80

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.cluster.local      
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:    
    - id : Cluster1-bsf-instance1
      type: BSF
      owner: Cluster1
      fqdn: bsf-ocbsf-config-mgmt.bsf.svc.cluster.local
      port: 80
    - id : Cluster2-bsf-instance1
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local
      port: 80
    - id : Cluster2-bsf-instance2
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local
      port: 80

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-bsf-instance1
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local  
      port: 80
    - id : Cluster2-bsf-instance2
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local  
      port: 80

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-bsf-instance1
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf1.svc.cluster.local 
      port: 80
    - id : Cluster2-bsf-instance2
      type: BSF
      owner: Cluster2
      fqdn: bsf-ocbsf-config-mgmt.bsf2.svc.cluster.local 
      port: 80

NRF Instances Configuration Examples

NRF Single Cluster Deployment Instance Configuration Examples

NRF Single-Cluster Configuration

CNCC Configuration

global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local      
      port: 80   
  instances:
    - id : Cluster1-nrf-instance1
      type: NRF
      owner: Cluster1
      fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local
      port: 80

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

global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443   
  instances:
    - id : Cluster1-nrf-instance1
      type: NRF
      owner: Cluster1
      fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local
      port: 80

NRF Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx  
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1     
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80 
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id : Cluster1-nrf-instance1
      type: NRF
      owner: Cluster1
      fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local 
      port: 80
    - id : Cluster2-nrf-instance1
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local 
      port: 80
    - id : Cluster2-nrf-instance2
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local 
      port: 80

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.cluster.local      
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:    
    - id : Cluster1-nrf-instance1
      type: NRF
      owner: Cluster1
      fqdn: ocnrf-nrfconfiguration.nrf.svc.cluster.local  
      port: 80
    - id : Cluster2-nrf-instance1
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local  
      port: 80
    - id : Cluster2-nrf-instance2
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local  
      port: 80

Note:

In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-nrf-instance1
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local
      port: 80
    - id : Cluster2-nrf-instance2
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local
      port: 80

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-nrf-instance1
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf1.svc.cluster.local 
      port: 80
    - id : Cluster2-nrf-instance2
      type: NRF
      owner: Cluster2
      fqdn: ocnrf-nrfconfiguration.nrf2.svc.cluster.local 
      port: 80

NSSF Instances Configuration Examples

NSSF Single Cluster Deployment Instance Configuration Examples

NSSF Single Cluster Configuration

CNCC Configuration 


global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 80  
  instances:
    - id : Cluster1-nssf-instance1
      type: NSSF
      owner: Cluster1
      fqdn: ocnssf-nsconfig.ocnssf-nssf.svc.cluster.local        
      port: 80

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

global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443
  instances:
    - id : Cluster1-nssf-instance1
      type: NSSF
      owner: Cluster1
      fqdn: ocnssf-nsconfig.ocnssf-nssf.svc.cluster.local
      port: 80

NSSF Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1    
      role: Cluster1  
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local       
      port: 80
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:    
    - id : Cluster1-nssf-instance1
      type: NSSF
      owner: Cluster1
      fqdn: ocnssf-nsconfig.ocnssf-nssf1.svc.cluster.local   
      port: 80    
    - id : Cluster2-nssf-instance1
      type: NSSF
      owner: Cluster2
      fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
      port: 80

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.cluster.local       
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:          
    - id : Cluster1-nssf-instance1
      type: NSSF
      owner: Cluster1
      fqdn: ocnssf-nsconfig.ocnssf-nssf1.svc.cluster.local
      port: 80   
    - id : Cluster2-nssf-instance1
      type: NSSF
      owner: Cluster2
      fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
      port: 80

Note:

In this example local NF and A-CNCC Core is considered to be deployed in Manager Cluster, its a 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-nssf-instance1
      type: NSSF
      owner: Cluster2
      fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
      port: 80

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-nssf-instance1
      type: NSSF
      owner: Cluster2
      fqdn: ocnssf-nsconfig.ocnssf-nssf2.svc.cluster.local
      port: 80

Policy Instances Configuration Examples

Policy Single Cluster Deployment Instance Configuration Examples

CNCC Configuration

global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local      
      port: 80   
  instances:
    - id : Cluster1-policy-instance1
      type: POLICY
      owner: Cluster1
      fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local   
      port: 80

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

global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443   
  instances:
    - id : Cluster1-policy-instance1
      type: POLICY
      owner: Cluster1
      fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local  
      port: 80

Policy Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx   
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1     
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80 
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id : Cluster1-policy-instance1
      type: POLICY
      owner: Cluster1
      fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance1
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance2
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
      port: 80

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.cluster.local      
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:    
    - id : Cluster1-policy-instance1
      type: POLICY
      owner: Cluster1
      fqdn: policy-occnp-config-mgmt.policy.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance1
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance2
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
      port: 80

Note:

In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-policy-instance1
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance2
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
      port: 80

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-policy-instance1
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy1.svc.cluster.local
      port: 80
    - id : Cluster2-policy-instance2
      type: POLICY
      owner: Cluster2
      fqdn: policy-occnp-config-mgmt.policy2.svc.cluster.local
      port: 80

SCP Instances Configuration Examples

SCP Single Cluster Deployment Instance Configuration Examples

SCP Single Cluster Configuration

CNCC Configuration
global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local      
      port: 80   
  instances:
    - id : Cluster1-scp-instance1
      type: SCP
      owner: Cluster1
      fqdn: ocscp-scpc-configuration.scp.svc.cluster.local  
      port: 80

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
global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443   
  instances:
    - id : Cluster1-scp-instance1
      type: SCP
      owner: Cluster1
      fqdn: ocscp-scpc-configuration.scp.svc.cluster.local  
      port: 80

SCP Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1 and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx  
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1     
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80 
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id : Cluster1-scp-instance1
      type: SCP
      owner: Cluster1
      fqdn: ocscp-scpc-configuration.scp.svc.cluster.local  
      port: 80
    - id : Cluster2-scp-instance1
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local  
      port: 80
    - id : Cluster2-scp-instance2
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local  
      port: 80

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.cluster.local      
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:    
    - id : Cluster1-scp-instance1
      type: SCP
      owner: Cluster1
      fqdn: ocscp-scpc-configuration.scp.svc.cluster.local
      port: 80
    - id : Cluster2-scp-instance1
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
      port: 80
    - id : Cluster2-scp-instance2
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
      port: 80

Note:

In this example local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-scp-instance1
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
      port: 80
    - id : Cluster2-scp-instance2
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
      port: 80

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-scp-instance1
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp1.svc.cluster.local
      port: 80
    - id : Cluster2-scp-instance2
      type: SCP
      owner: Cluster2
      fqdn: ocscp-scpc-configuration.scp2.svc.cluster.local
      port: 80

SEPP Instances Configuration Examples

SEPP Single Cluster Deployment Instance Configuration Examples

SEPP Single Cluster Configuration

CNCC Configuration
global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local      
      port: 80   
  instances:
    - id : Cluster1-sepp-instance1
      type: SEPP
      owner: Cluster1
      fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local      
      port: 80

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 Core
global:
 
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
 
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443   
  instances:
    - id : Cluster1-sepp-instance1
      type: SEPP
      owner: Cluster1
      fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local        
      port: 80

SEPP Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1, A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx   
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1     
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80 
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id : Cluster1-sepp-instance1
      type: SEPP
      owner: Cluster1
      fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local  
      port: 80
    - id : Cluster2-sepp-instance1
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local 
      port: 80
    - id : Cluster2-sepp-instance2
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local 
      port: 80

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.cluster.local      
      port: 443
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:    
    - id : Cluster1-sepp-instance1
      type: SEPP
      owner: Cluster1
      fqdn: ocsepp-config-mgr-svc.sepp.svc.cluster.local  
      port: 80
    - id : Cluster2-sepp-instance1
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local 
      port: 80
    - id : Cluster2-sepp-instance2
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local 
      port: 80

Note:

In this example, the local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-sepp-instance1
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local 
      port: 80
    - id : Cluster2-sepp-instance2
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local 
      port: 80

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-sepp-instance1
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp1.svc.cluster.local 
      port: 80
    - id : Cluster2-sepp-instance2
      type: SEPP
      owner: Cluster2
      fqdn: ocsepp-config-mgr-svc.sepp2.svc.cluster.local 
      port: 80

UDR Instances Configuration Examples

UDR Single Cluster Deployment Instance Configuration Examples

UDR Single Cluster Configuration

CNCC Configuration
global:
   
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
  
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 80  
  instances:
    - id : Cluster1-udr-instance1
      type: UDR-PROV
      owner: Cluster1
      fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
      port: 80
    - id : Cluster1-udr-instance1
      type: UDR-CONFIG
      owner: Cluster1
      fqdn: udr1-nudr-config.udr.svc.cluster.local
      port: 80

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
global:
   
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true
  
  isMultiClusterDeployment: false
  # 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.cluster.local
      port: 443  
  instances:
    - id : Cluster1-udr-instance1
      type: UDR-PROV
      owner: Cluster1
      fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
      port: 80
    - id : Cluster1-udr-instance1
      type: UDR-CONFIG
      owner: Cluster1
      fqdn: udr1-nudr-config.udr.svc.cluster.local
      port: 80

UDR Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1  
      role: Cluster1    
      fqdn: cncc-acore-ingress-gateway.cncc.svc.cluster.local      
      port: 80    
    - id: Cluster2  
      role: Cluster2    
      ip: 10.xx.xx.xx   
      port: 80
  instances:
    - id : Cluster1-udr-instance1
      type: UDR-PROV
      owner: Cluster1
      fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
      port: 80
    - id : Cluster1-udr-instance1
      type: UDR-CONFIG
      owner: Cluster1
      fqdn: udr1-nudr-config.udr.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-PROV
      owner: Cluster2
      fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-CONFIG
      owner: Cluster2
      fqdn: udr1-nudr-config.udr1.svc.cluster.local
      port: 80

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)

lobal:
  
  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.cluster.local      
      port: 443    
    - id: Cluster2  
      role: Cluster2
      scheme: https   
      ip: 10.xx.xx.xx   
      port: 443
  instances:
    - id : Cluster1-udr-instance1
      type: UDR-PROV
      owner: Cluster1
      fqdn: udr1-ingressgateway-prov.udr.svc.cluster.local
      port: 80
    - id : Cluster1-udr-instance1
      type: UDR-CONFIG
      owner: Cluster1
      fqdn: udr1-nudr-config.udr.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-PROV
      owner: Cluster2
      fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-CONFIG
      owner: Cluster2
      fqdn: udr1-nudr-config.udr1.svc.cluster.local
      port: 80

Note:

In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-udr-instance1
      type: UDR-PROV
      owner: Cluster2
      fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-CONFIG
      owner: Cluster2
      fqdn: udr1-nudr-config.udr1.svc.cluster.local
      port: 80

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-udr-instance1
      type: UDR-PROV
      owner: Cluster2
      fqdn: udr1-ingressgateway-prov.udr1.svc.cluster.local
      port: 80
    - id : Cluster2-udr-instance1
      type: UDR-CONFIG
      owner: Cluster2
      fqdn: udr1-nudr-config.udr1.svc.cluster.local
      port: 80

Common Service Instances Configuration Examples

Common Service Single Cluster Deployment Instance Configuration Examples

Common Service Single Cluster Configuration

CNCC CNCC Configuration
global:
   
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true  
 
  isMultiClusterDeployment: false
  # 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.jazz
      port: 80  
  instances:    
    - id: Cluster1-grafana
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /jazz/grafana
    - id: Cluster1-kibana
      type: CS
      owner: Cluster1
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /jazz/kibana    
    - id: Cluster1-jaeger
      type: CS
      owner: Cluster1
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /jazz/jaeger
    - id: Cluster1-prometheus
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /jazz/prometheus
    - id: Cluster1-alertmanager
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /jazz/alertmanager

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
global:
   
  cncc-iam:
    enabled: true
  mcncc-core:
    enabled: true
  acncc-core:
    enabled: true  
 
  isMultiClusterDeployment: false
  # 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.jazz
      port: 443
  instances:    
    - id: Cluster1-grafana
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /jazz/grafana
    - id: Cluster1-kibana
      type: CS
      owner: Cluster1
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /jazz/kibana    
    - id: Cluster1-jaeger
      type: CS
      owner: Cluster1
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /jazz/jaeger
    - id: Cluster1-prometheus
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /jazz/prometheus
    - id: Cluster1-alertmanager
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /jazz/alertmanager

Common Service Multicluster Deployment Instance Configuration Examples

(M-CNCC Core on Cluster1 , A-CNCC Core on Cluster1, and A-CNCC Core on Cluster2)

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
      ip: 10.xx.xx.xx    
  mCnccCores:
    - id: Cluster1
  aCnccs:
    - id: Cluster1
      role: Cluster1      
      fqdn: cncc-acore-ingress-gateway.cncc.svc.jazz     
      port: 80  
    - id: Cluster2
      role: Cluster2
      ip: 10.xx.xx.xx
      port: 80
  instances:
    - id: Cluster1-grafana
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /jazz/grafana
    - id: Cluster1-kibana
      type: CS
      owner: Cluster1
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /jazz/kibana    
    - id: Cluster1-jaeger
      type: CS
      owner: Cluster1
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /jazz/jaeger
    - id: Cluster1-prometheus
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /jazz/prometheus
    - id: Cluster1-alertmanager
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /jazz/alertmanager
    - id: Cluster2-grafana
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /rivendell-2210/grafana
    - id: Cluster2-kibana
      type: CS
      owner: Cluster2
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /rivendell-2210/kibana    
    - id: Cluster2-jaeger
      type: CS
      owner: Cluster2
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /rivendell-2210/jaeger
    - id: Cluster2-prometheus
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /rivendell-2210/prometheus
    - id: Cluster2-alertmanager
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /rivendell-2210/alertmanager

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.jazz    
      port: 443 
    - id: Cluster2
      role: Cluster2
      scheme: https
      ip: 10.xx.xx.xx
      port: 443
  instances:
    - id: Cluster1-grafana
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /jazz/grafana
    - id: Cluster1-kibana
      type: CS
      owner: Cluster1
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /jazz/kibana    
    - id: Cluster1-jaeger
      type: CS
      owner: Cluster1
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /jazz/jaeger
    - id: Cluster1-prometheus
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /jazz/prometheus
    - id: Cluster1-alertmanager
      type: CS
      owner: Cluster1
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /jazz/alertmanager
    - id: Cluster2-grafana
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /rivendell-2210/grafana
    - id: Cluster2-kibana
      type: CS
      owner: Cluster2
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /rivendell-2210/kibana    
    - id: Cluster2-jaeger
      type: CS
      owner: Cluster2
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /rivendell-2210/jaeger
    - id: Cluster2-prometheus
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /rivendell-2210/prometheus
    - id: Cluster2-alertmanager
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /rivendell-2210/alertmanager

Note:

In this example, local NF and A-CNCC Core are considered to be deployed in Manager Cluster, it is 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-grafana
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /rivendell-2210/grafana
    - id: Cluster2-kibana
      type: CS
      owner: Cluster2
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /rivendell-2210/kibana    
    - id: Cluster2-jaeger
      type: CS
      owner: Cluster2
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /rivendell-2210/jaeger
    - id: Cluster2-prometheus
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /rivendell-2210/prometheus
    - id: Cluster2-alertmanager
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /rivendell-2210/alertmanager

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-grafana
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-grafana.occne-infra.svc
      apiPrefix: /rivendell-2210/grafana
    - id: Cluster2-kibana
      type: CS
      owner: Cluster2
      fqdn: occne-kibana.occne-infra.svc
      apiPrefix: /rivendell-2210/kibana    
    - id: Cluster2-jaeger
      type: CS
      owner: Cluster2
      fqdn: occne-tracer-jaeger-query.occne-infra.svc
      apiPrefix: /rivendell-2210/jaeger
    - id: Cluster2-prometheus
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-prometheus.occne-infra.svc
      apiPrefix: /rivendell-2210/prometheus
    - id: Cluster2-alertmanager
      type: CS
      owner: Cluster2
      fqdn: occne-kube-prom-stack-kube-alertmanager.occne-infra.svc
      apiPrefix: /rivendell-2210/alertmanager