Merge pull request #269825 from SarahBoris/sb_03212024

update how to configure network function for review

Author: JamesJBarnett

articles/operator-5g-core/how-to-configure-network-function.md

@@ -1,15 +1,15 @@
 ---
-title: Configure a network function in Azure Operator 5G Core Preview
+title: Configure Azure Operator 5G Core Preview network functions
 description: Learn the high-level process for configuring a network function.
 author: HollyCl
 ms.author: HollyCl
 ms.service: azure-operator-5g-core
 ms.topic: how-to #required; leave this attribute/value as-is
-ms.date: 02/22/2024
+ms.date: 03/21/2024
 
 ---
 
-# Configure a network function in Azure Operator 5G Core Preview
+# Configure Azure Operator 5G Core Preview network functions
 
 Azure Operator 5G Core Preview supports  direct configuration of the first party packet core network functions deployed on Azure and Nexus by:
 
@@ -18,6 +18,34 @@ Azure Operator 5G Core Preview supports  direct configuration of the first party
 
 Note that many concurrent configuration user sessions are supported.
 
+## Prerequisites
+
+Before you SSH to your Azure Operator 5G Core, complete the following prerequisites: 
+
+1. You must be able to manage your Kubernetes cluster using the Kubernetes command-line client, `kubectl`. `kubectl` is already installed if you use Azure Cloud Shell. To install `kubectl` locally, use the `az aks install-cli` command.
+
+1. After installing `kubectl,` you need the kube.conf file to connect to your Kubernetes cluster. If you’re using Azure Cloud Shell, the kube.conf file is automatically configured for you. 
+
+    If you’re running commands locally, follow these steps: 
+
+    1. Ensure you have the kube.conf file from your Kubernetes cluster.  
+
+    1. Use scp (secure copy) or any other secure method to transfer the file to your local machine. Place the kube.conf file in the ~/.kube/config directory.
+
+## Connect to an Azure Operator 5G Core Preview network function using SSH
+
+1. Obtain the IP address provided to the cfgmgr service's load balancer. Enter the following ```kubectl``` command or use the cfgmgr load balancer IP address specified during deployment:  
+
+    `kubectl get svc -n fed-<nf_name>` \
+    where `<nf_name>` is the name of the network function (for example, smf).
+
+1. Use the cfgmgr load balancer IP address to SSH into the network function and configure it:
+
+    `ssh admin@<nf_cfgmgr_svc_lb_ip>` \
+    where `<nf_cfgmgr_svc_lb_ip>` is the cfgmgr load balancer IP address for the network function.
+
+1. Use the `config` command to enter config mode and configure the network function.
+
 ## Additional information
 
 For more information, see the documentation for the [Configuration Manager](https://manuals.metaswitch.com/UC/4.3.0/UnityCloud_Overview/Content/Microservices/Shared/Microservices/Config_Manager.htm).

articles/operator-5g-core/how-to-deploy-observability.md

@@ -10,27 +10,31 @@ ms.date: 02/22/2024
 #CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
 ---
 
-# Deploy Azure Operator 5G Core observability (preview) on Azure Kubernetes Services (AKS) or Nexus Azure Kubernetes Services (NAKS)
+# Deploy Azure Operator 5G Core Preview observability services
 
 Use the following Azure CLI commands to deploy observability resources for Azure Operator 5G Core Preview.
 
-## Deploy observability
+> [!IMPORTANT]
+> You must deploy the clusterServices resource before deploying observability services. 
 
+## Deploy observability
 
 ```azurecli
-New-AzResourceGroupDeployment ` 
-
--Name <DEPLOYMENT NAME> ` 
-
--ResourceGroupName <RESOURCE GROUP> ` 
-
--TemplateFile ./releases/2311.0-1/AKS/bicep/obsvTemplate.bicep ` 
-
--TemplateParameterFile ./releases/2311.0-1/AKS/params/obsvParams.json ` 
-
--resourceName <RESOURCE NAME> –Verbose
+$ export resourceGroupName <Name of resource group> 
+$ export templateFile <Path to bicep scripts>
+$ export resourceName <Choose name for the AO5GC resource – note the same resourceName should be used for clusterServices and all associated NFs> 
+$ export location <Azure region where resources are deployed> 
+$ export templateParamsFile <Path to bicep script parameters file> 
+
+$ az deployment group create  
+--resource-group $resourceGroupName \ 
+--template-file $templateFile \ 
+--parameters resourceName=$resourceName \ 
+--parameters locationName=$location \ 
+--parameters $templateParamsFile 
+-- verbose 
 ```
 
 ## Next step
 
-- [Deploy a network function on Azure Kubernetes Services or Nexus Azure Kubernetes Services](how-to-deploy-network-functions.md)
+- [Deploy an Azure Operator 5G Core network function](how-to-deploy-network-functions.md)