You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-5g-core/quickstart-configure-extension-for-status-monitoring.md
+15-22Lines changed: 15 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
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
3
3
description: Learn how to ensure your deployment is running at its highest capacity by performing health checks post-deployment.
4
4
author: HollyCl
5
5
ms.author: HollyCl
@@ -11,7 +11,7 @@ ms.date: 02/21/2024
11
11
12
12
#CustomerIntent: As a < type of user >, I want < what? > so that < why? >.
13
13
---
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
15
15
16
16
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.
17
17
@@ -21,16 +21,19 @@ After Azure Operator 5G Core Preview is deployed, you can perform health and con
21
21
1. Set the subscription: `az account set -s <subscriptionName>`
22
22
1. Run the following commands to install the CLI extensions:
23
23
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
+
```
29
29
30
30
## Configure ARC for the Kubernetes/Azure Kubernetes Services Cluster
az connectedk8s connect --name <ConnectedK8sName> --resource-group <ResourceGroupName>
36
+
```
34
37
35
38
## Deploy the Azure Operator 5G Core Preview extension
36
39
@@ -47,8 +50,11 @@ Enter the following command to configure the ARC:
47
50
--auto-upgrade true
48
51
```
49
52
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:
The namespace and all necessary Azure Operator 5G Core extension pods, configuration maps, and services are created within the namespace.
53
59
54
60
To delete the Azure Operator 5G Core extension, you can run the following command:
@@ -60,19 +66,6 @@ az k8s-extension delete \
60
66
--resource-group <ResourceGroupName> \
61
67
--cluster-type connectedClusters \
62
68
```
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:
0 commit comments