Skip to content

Commit 383e350

Browse files
committed
apply review comments articles 3 and 5
1 parent 0a17e70 commit 383e350

File tree

2 files changed

+29
-19
lines changed

2 files changed

+29
-19
lines changed

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

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,23 +20,29 @@ Note that many concurrent configuration user sessions are supported.
2020

2121
## Prerequisites
2222

23-
Before you can successfully SSH to your Azure Operator 5G Core, you must:
23+
Before you SSH to your Azure Operator 5G Core, complete the following prerequisites:
2424

25-
1. Install `kubectl`. `kubectl` is the Kubernetes command-line tool that allows you to manage Kubernetes clusters.
25+
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.
2626

27-
1. Copy the kube.conf file from its source to the ~/.kube/config directory. You can copy the file using scp (secure copy) or any other secure method.
27+
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.
28+
29+
If you’re running commands locally, follow these steps:
30+
31+
1. Ensure you have the kube.conf file from your Kubernetes cluster.
32+
33+
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.
2834

2935
## Connect to an Azure Operator 5G Core Preview network function using SSH
3036

3137
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:
3238

3339
`kubectl get svc -n fed-<nf_name>` \
34-
where <nf_name> is the name of the network function (for example, smf).
40+
where `<nf_name>` is the name of the network function (for example, smf).
3541

3642
1. Use the cfgmgr load balancer IP address to SSH into the network function and configure it:
3743

3844
`ssh admin@<nf_cfgmgr_svc_lb_ip>` \
39-
where <nf_cfgmgr_svc_lb_ip> is the cfgmgr load balancer IP address for the network function.
45+
where `<nf_cfgmgr_svc_lb_ip>` is the cfgmgr load balancer IP address for the network function.
4046

4147
1. Use the `config` command to enter config mode and configure the network function.
4248

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

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -10,27 +10,31 @@ ms.date: 02/22/2024
1010
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
1111
---
1212

13-
# Deploy Azure Operator 5G Core observability (preview) on Azure Kubernetes Services (AKS) or Nexus Azure Kubernetes Services (NAKS)
13+
# Deploy Azure Operator 5G Core Preview observability services
1414

1515
Use the following Azure CLI commands to deploy observability resources for Azure Operator 5G Core Preview.
1616

17-
## Deploy observability
17+
> [!IMPORTANT]
18+
> You must deploy the clusterServices resource before deploying observability services.
1819
20+
## Deploy observability
1921

2022
```azurecli
21-
New-AzResourceGroupDeployment `
22-
23-
-Name <DEPLOYMENT NAME> `
24-
25-
-ResourceGroupName <RESOURCE GROUP> `
26-
27-
-TemplateFile ./releases/2311.0-1/AKS/bicep/obsvTemplate.bicep `
28-
29-
-TemplateParameterFile ./releases/2311.0-1/AKS/params/obsvParams.json `
30-
31-
-resourceName <RESOURCE NAME> –Verbose
23+
$ export resourceGroupName <Name of resource group>
24+
$ export templateFile <Path to bicep scripts>
25+
$ export resourceName <Choose name for the AO5GC resource – note the same resourceName should be used for clusterServices and all associated NFs>
26+
$ export location <Azure region where resources are deployed>
27+
$ export templateParamsFile <Path to bicep script parameters file>
28+
29+
$ az deployment group create
30+
--resource-group $resourceGroupName \
31+
--template-file $templateFile \
32+
--parameters resourceName=$resourceName \
33+
--parameters locationName=$location \
34+
--parameters $templateParamsFile
35+
-- verbose
3236
```
3337

3438
## Next step
3539

36-
- [Deploy a network function on Azure Kubernetes Services or Nexus Azure Kubernetes Services](how-to-deploy-network-functions.md)
40+
- [Deploy an Azure Operator 5G Core network function](how-to-deploy-network-functions.md)

0 commit comments

Comments
 (0)