What's New in This Guide
This section introduces the documentation updates for Release 24.3.x.
Release 24.3.0 -G10456-01, October 2024
- General Updates:
- Updated the release number to 24.3.0 in the entire document.
- Installation Updates:
- Updated the software versions in Software Requirements.
- Added the Configuring Cloud Native Load Balancer (CNLB) IPs section with details on cofiguring the following:
- Configuring CNLB IP for M-CNCC IAM
- Configuring CNLB IP for M-CNCC Core
- Configuring CNLB IP for A-CNCC Core
- Configuring Annotation for Egress Traffic for M-CNCC IAM
- Enabling Additional Settings in M-CNCC IAM
- Added the Automate Certificate Lifecycle Management Using OCCM section with details on support for automated certificate lifecycle management using OCCM.
- Added Configuring M-CNCC IAM to Enable Additional Settings.
- Added a note on configuring the
cnccDeploymentModeto deploy CNC Console in a Dual Stack environment in Installing CNC Console Package. - Added a note on assigning Static IP addresses in case of IPv4_IPv6 or IPv6_IPv4 in Installing CNC Console Package.
- Updated the Global Configuration Options section with the following:
- Added the
global.cnccDeploymentModeparameter to specify the mode in which console services components can be deployed. - Added the
global.tlsVersionparameter to indicate the TLS version. - Added the
global.cipherSuitesparameter to indicate the allowed Ciphers suites. - Added the
global.clientDisabledExtensionparameter to disable the the extension sent by messages originated by clients (ClientHello). - Added the
global.serverDisabledExtensionparameter to disable the extension sent by messages originated by servers (ServerHello). - Added the
global.tlsNamedGroupsparameter to provide a list of values sent in the supported_groups extension. - Added the
global.clientSignatureSchemesparameter to provide a list of values sent in the signature_algorithms extension. - Added the following parameters as part of security context
constraint configuration:
global.enablePodSecurityContextglobal.podSecurityContext.runAsNonRootglobal.podSecurityContext.runAsUserglobal.enableContainerSecurityContextglobal.containerSecurityContext.readOnlyRootFilesystemglobal.containerSecurityContext.allowPrivilegeEscalationglobal.containerSecurityContext.privilegedglobal.containerSecurityContext.runAsNonRootglobal.containerSecurityContext.runAsUserglobal.containerSecurityContext.capabilities.drop
- Added the
- Updated the CNC Console IAM Configuration Parameters section with the following:
- Added the
cncc-iam.global.iamSettingEnabledparameter. - Added the
cncc-iam.kc.global.deploymentModeparameter to define the mode in which CNC Console IAM kc service component can be deployed. - Added the
cncc-iam.ingress-gateway.global.deploymentModeparameter to define the mode in which CNC Console IAM ingress gateway service component can be deployed. - Added the
cncc-iam.kc.keycloak.podAnnotationsparameter as a custom annotations that must be added for traffic segregated egress traffic from CNC Console IAM in Traffic Segregation supported cluster. - Added the
cncc-iam.ingress-gateway.ports.containerPortNameparameter to define the name of the container port for Ingress Gateway. - Added the
cncc-iam.ingress-gateway.ports.containersslPortNameparameter to define the name of containerssl port for Ingress Gateway. - Updated the
cncc-iam.ingress-gateway.clientDisabledExtensionparameter to indicate that the values will be set by global.clientDisabledExtension. - Updated the
cncc-iam.ingress-gateway.serverDisabledExtensionparameter to indicate that the values will be set by global.serverDisabledExtension. - Updated the
cncc-iam.ingress-gateway.tlsNamedGroupsparameter to indicate that the values will be set by global.tlsNamedGroups. - Updated the
cncc-iam.ingress-gateway.clientSignatureSchemesparameter to indicate that the values will be set by global.clientSignatureSchemes. - Updated the
cncc-iam.ingress-gateway.service.ssl.tlsVersionparameter to indicate that the values will be set by global.tlsVersion. - Updated the
cncc-iam.ingress-gateway.cipherSuitesparameter to indicate that the values will be set by global.cipherSuites. - Added the following parameters as part of security
context constraint configuration:
Global Parameters:
cncc-iam.global.hook.enableContainerSecurityContextcncc-iam.global.hook.containerSecurityContext.readOnlyRootFilesystemcncc-iam.global.hook.containerSecurityContext.allowPrivilegeEscalationcncc-iam.global.hook.containerSecurityContext.privilegedcncc-iam.global.hook.containerSecurityContext.runAsNonRootcncc-iam.global.hook.containerSecurityContext.runAsUsercncc-iam.global.hook.containerSecurityContext.capabilities.dropIAM Backend Parameters:
cncc-iam.kc.enablePodSecurityContextcncc-iam.kc.podSecurityContext.runAsNonRootcncc-iam.kc.podSecurityContext.runAsUsercncc-iam.kc.healthcheck.enableContainerSecurityContextcncc-iam.kc.healthcheck.containerSecurityContext.readOnlyRootFilesystemcncc-iam.kc.healthcheck.containerSecurityContext.allowPrivilegeEscalationcncc-iam.kc.healthcheck.containerSecurityContext.privilegedcncc-iam.kc.healthcheck.containerSecurityContext.runAsNonRootcncc-iam.kc.healthcheck.containerSecurityContext.runAsUsercncc-iam.kc.healthcheck.containerSecurityContext.capabilities.dropcncc-iam.kc.enablePodSecurityContextcncc-iam.kc.podSecurityContext.runAsNonRootcncc-iam.kc.podSecurityContext.runAsUserglobal.enablePodSecurityContextglobal.podSecurityContext.runAsNonRootglobal.podSecurityContext.runAsUsercncc-iam.kc.keycloak.enableContainerSecurityContextcncc-iam.kc.keycloak.containerSecurityContext.readOnlyRootFilesystemcncc-iam.kc.keycloak.containerSecurityContext.allowPrivilegeEscalationcncc-iam.kc.keycloak.containerSecurityContext.privilegedcncc-iam.kc.keycloak.containerSecurityContext.runAsNonRootcncc-iam.kc.keycloak.containerSecurityContext.runAsUsercncc-iam.kc.keycloak.containerSecurityContext.capabilities.drop
- Added the
- Updated the M-CNCC Core Configuration Options section with the following:
- Added the
mcncc-core.cmservice.global.deploymentModeparameter to define the mode in which cmservice service component can be deployed. - Added the
mcncc-core.ingress-gateway.global.deploymentModeparameter to define the mode in which M-CNCC Core ingress gateway service component can be deployed. - Added the
ingress-gateway.ports.containerPortNameparameter to define the name of the container port for Ingress Gateway. - Added the
ingress-gateway.ports.containersslPortNameparameter to define the name of the container SSL port for Ingress Gateway. - Updated the
ingress-gateway.clientDisabledExtensionparameter to indicate that the values will be set by global.clientDisabledExtension. - Updated the
ingress-gateway.serverDisabledExtensionparameter to indicate that the values will be set by global.serverDisabledExtension. - Updated the
ingress-gateway.tlsNamedGroupsparameter to indicate that the values will be set by global.tlsNamedGroups. - Updated the
ingress-gateway.clientSignatureSchemesparameter to indicate that the values will be set by global.clientSignatureSchemes. - Updated the
ingress-gateway.service.ssl.tlsVersionparameter to indicate that the values will be set by global.tlsVersion. - Updated the
ingress-gateway.cipherSuitesparameter to indicate that the values will be set by global.cipherSuites. - Added the following parameters as part of security context
constraint configuration:
cmservice.enablePodSecurityContextcmservice.podSecurityContext.runAsNonRootcmservice.podSecurityContext.runAsUsercmservice.enableContainerSecurityContextcmservice.containerSecurityContext.readOnlyRootFilesystemcmservice.containerSecurityContext.allowPrivilegeEscalationcmservice.containerSecurityContext.privilegedcmservice.containerSecurityContext.runAsNonRootcmservice.containerSecurityContext.runAsUsercmservice.containerSecurityContext.capabilities.dropcmservice.enablePodSecurityContextcmservice.podSecurityContext.runAsNonRootcmservice.podSecurityContext.runAsUser
- Added the
- Updated the A-CNCC Core Configuration Options section with the following:
- Added the
acncc-core.ingress-gateway.global.deploymentModeparameter to define the mode in which A-CNCC core ingress gateway service component can be deployed. - Added the
ingress-gateway.ports.containerPortNameparameter to define the http port of the container for Ingress Gateway. - Added the
ingress-gateway.ports.containersslPortNameparameter to define the http port of the container SSL for Ingress Gateway. - Updated the
ingress-gateway.clientDisabledExtensionparameter to indicate that the values will be set by global.clientDisabledExtension. - Updated the
ingress-gateway.serverDisabledExtensionparameter to indicate that the values will be set by global.serverDisabledExtension. - Updated the
ingress-gateway.tlsNamedGroupsparameter to indicate that the values will be set by global.tlsNamedGroups. - Updated the
ingress-gateway.clientSignatureSchemesparameter to indicate that the values will be set by global.clientSignatureSchemes. - Updated the
ingress-gateway.service.ssl.tlsVersionparameter to indicate that the values will be set by global.tlsVersion. - Updated the
ingress-gateway.cipherSuitesparameter to indicate that the values will be set by global.cipherSuites.
- Added the
- Updated the NWDAF instance configuration examples in the NWDAF Instance Configuration Examples section.
- Upgrade, Rollback, and Uninstall Updates:
- Added a note in the Upgrading CNC Console section to update the CNC Console custom value file and set the
cnccDeploymentModeto the desired value before performing the CNC Console Helm upgrade. - Updated the note in the CNC Console Upgrade section to highlight that the mCnccIams.port configuration must be added only if port is other than default 80 or 443
- Added the Preupgrade Procedure for Dual Stack Networking section with the procedure that must be performed before upgrading CNC Console in case of dual stack networking.
- Added the Enabling Automated Certificate Lifecycle Management through OCCM during Console Upgrade section with the procedure to upgrade automated certificate lifecycle management using OCCM.
- Added the Prerollback Procedure for Dual Stack Networking section with the procedure that must be performed before rolling back CNC Console in case of dual stack networking.
- Added the unresolvable-reference.html#GUID-11D1D9E8-A65D-40DB-A896-61B89B097965 section with the procedure to rollback from automated certificate management to manual certificate management using OCCM.
- Updated the upgrade version in Supported Upgrade Paths.
- Updated the rollback version in Supported Rollback Paths.
- Added a note in the Upgrading CNC Console section to update the CNC Console custom value file and set the