Skip to content

Commit 12cd547

Browse files
Merge pull request #270657 from HollyCl/howto329
update perform health check article, and renamed. Updated redirect file
2 parents 8de2e91 + 43b001b commit 12cd547

File tree

2 files changed

+20
-22
lines changed

2 files changed

+20
-22
lines changed

.openpublishing.redirection.operator-5g-core.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,11 @@
4444
"source_path_from_root": "/articles/operator-5g-core/quickstart-deploy-network-functions.md",
4545
"redirect_url": "/azure/operator-5g-core/how-to-deploy-network-functions",
4646
"redirect_document_id": false
47+
},
48+
{
49+
"source_path_from_root": "/articles/operator-5g-core/quickstart-perform-checks-post-deployment.md",
50+
"redirect_url": "/azure/operator-5g-core/quickstart-configure-extension-for-status-monitoring",
51+
"redirect_document_id": false
4752
}
4853
]
4954
}

articles/operator-5g-core/quickstart-perform-checks-post-deployment.md renamed to articles/operator-5g-core/quickstart-configure-extension-for-status-monitoring.md

Lines changed: 15 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Performing health checks post-deployment in Azure Operator 5G Core Preview
2+
title: Configure the Azure Operator 5G Core extension for status monitoring
33
description: Learn how to ensure your deployment is running at its highest capacity by performing health checks post-deployment.
44
author: HollyCl
55
ms.author: HollyCl
@@ -11,7 +11,7 @@ ms.date: 02/21/2024
1111

1212
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
1313
---
14-
# Perform health and configuration checks post-deployment in Azure Operator 5G Core Preview
14+
# Configure the Azure Operator 5G Core Preview extension for status monitoring
1515

1616
After Azure Operator 5G Core Preview is deployed, you can perform health and configuration checks on the deployment. You must enable an ARC extension to monitor your deployment.
1717

@@ -21,16 +21,19 @@ After Azure Operator 5G Core Preview is deployed, you can perform health and con
2121
1. Set the subscription: `az account set -s <subscriptionName>`
2222
1. Run the following commands to install the CLI extensions:
2323

24-
`az extension add --yes --name connectedk8s`
25-
26-
`az extension add --yes --name k8s-configuration`
27-
28-
`az extension add --yes --name k8s-extension`
24+
```azurecli
25+
az extension add --yes --name connectedk8s
26+
az extension add --yes --name k8s-configuration
27+
az extension add --yes --name k8s-extension
28+
```
2929

3030
## Configure ARC for the Kubernetes/Azure Kubernetes Services Cluster
3131

3232
Enter the following command to configure the ARC:
33-
`az connectedk8s connect --name <ConnectedK8sName> --resource-group <ResourceGroupName>`
33+
34+
```azurecli
35+
az connectedk8s connect --name <ConnectedK8sName> --resource-group <ResourceGroupName>
36+
```
3437

3538
## Deploy the Azure Operator 5G Core Preview extension
3639

@@ -47,8 +50,11 @@ Enter the following command to configure the ARC:
4750
--auto-upgrade true
4851
```
4952
50-
2. Run the `kubectl label namespace ao5gc-monitor name=ao5gc-monitor` command to create a **name=ao5gc-monitor** label for the newly created **ao5gc-monitor** namespace.
53+
2. Run the following command to create a **name=ao5gc-monitor** label for the newly created **ao5gc-monitor** namespace:
5154
55+
```azurecli
56+
kubectl label namespace ao5gc-monitor name=ao5gc-monitor
57+
```
5258
The namespace and all necessary Azure Operator 5G Core extension pods, configuration maps, and services are created within the namespace.
5359
5460
To delete the Azure Operator 5G Core extension, you can run the following command:
@@ -60,19 +66,6 @@ az k8s-extension delete \
6066
--resource-group <ResourceGroupName> \
6167
--cluster-type connectedClusters \
6268
```
63-
64-
## Set permission for Azure Operator 5G Core Preview extension to access metrics
65-
66-
By default, the fed-prometheus cluster can be reached only from a small set of predefined namespaces. You must add the newly created **ao5gc-monitor** to the allowlist to obtain observability metrics.
67-
68-
To add the namespace to fed-prometheus:
69-
70-
1. Run the following command to add the helm values into a file for fed-prometheus:
71-
`helm get values fed-prometheus -n fed-prometheus –all> fed-prometheus_values.yaml`
72-
2. Add the **ao5gc-monitor** namespace under **ingressTrafficNamespaces** at the global level.
73-
1. Upgrade the fed-prometheus with the new helm values by running the following command:
74-
`helm upgrade fed-prometheus -n fed-prometheus fed-prometheus-4.3.0-46-rel-4-3-0.tgz -f fed-prometheus_values.yaml`
75-
7669
## Related content
7770

7871
- [Monitor the status of your Azure Operator 5G Core Preview deployment](quickstart-monitor-deployment-status.md)

0 commit comments

Comments
 (0)