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/openshift/howto-azure-monitor-v4.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,38 +54,39 @@ For Example:
54
54
55
55
## Configure agent data collection
56
56
57
-
By default, Monitoring Agent collects the {stdout; stderr} container logs of all the containers running in all the namespaces except kube-system. If you want to configure the container log collection specific to particular namespace(s), you can refer to https://docs.microsoft.com/azure/azure-monitor/insights/container-insights-agent-config. Here, you can configure Monitoring agent with desired data collection settings using config map.
57
+
By default, Monitoring Agent collects the {stdout; stderr} container logs of all the containers running in all the namespaces except kube-system. If you want to configure the container log collection specific to particular namespace or namespaces, you can refer to [Container Insights agent configuration](../azure-monitor/insights/container-insights-agent-config). Here, you can configure Monitoring agent with desired data collection settings using config map.
58
58
59
59
## Configure scraping of Prometheus metrics
60
60
61
-
Azure Monitor for containers scrapes the Prometheus metrics and ingest to the Azure Monitor backend. Refer to https://docs.microsoft.com/azure/azure-monitor/insights/container-insights-prometheus-integration for the instructions how to configure Prometheus scraping.
61
+
Azure Monitor for containers scrapes the Prometheus metrics and ingest to the Azure Monitor backend. Refer to [Container Insights Prometheus configuration](../azure-monitor/insights/container-insights-prometheus-integration) for the instructions how to configure Prometheus scraping.
62
62
63
63
After successful onboarding, navigate to https://aka.ms/azmon-containers-hybrid and select Environment as **"All"** to view your newly onboarded OpenShift v4 cluster.
64
64
65
65
## Disable monitoring
66
66
67
-
If you would like to disable monitoring, you can delete the Azure Monitor for Containers Helm chart using the below command to stop collecting and ingesting monitoring data to Azure Monitor for containers backend.
67
+
If you would like to disable monitoring, you can delete the Azure Monitor for Containers Helm chart using the following command to stop collecting and ingesting monitoring data to Azure Monitor for containers backend.
68
68
69
69
```bash
70
70
helm del azmon-containers-release-1
71
71
```
72
72
73
73
## Update monitoring
74
74
75
-
Rerun the onboarding script as in Onboarding section with the same parameter to get updated to latest Helm chart.
75
+
Rerun the onboarding script as described in the [Onboarding](#onboarding) section with the same parameter to get updated to latest Helm chart.
76
76
77
77
## After successful onboarding
78
78
79
-
Navigate to https://aka.ms/azmon-containers-hybrid and you should be able to see your newly enabled OpenShift/ARO v4 cluster with Health status in the Monitored Clusters Tab and you can get into deeper insights such as metrics, inventory, and logs etc. by clicking the Cluster column.
79
+
Navigate to [Hybrid Monitoring](https://aka.ms/azmon-containers-hybrid) and you should be able to see your newly enabled OpenShift/ARO v4 cluster with health status in the **Monitored Clusters** tab and you can get into deeper insights such as metrics, inventory, and logs and more by clicking the **Cluster** column.
80
80
81
81
## Supported features
82
82
83
-
For more information, see https://docs.microsoft.com/azure/azure-monitor/insights/container-insights-overview for more details on the supported features and functionality.
83
+
For more information, see [Container Insights overview](../azure-monitor/insights/container-insights-overview) for more details on the supported features and functionality.
Copy file name to clipboardExpand all lines: articles/openshift/howto-using-azure-redhat-openshift.md
+85-41Lines changed: 85 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ keywords: aro, openshift, az aro, red hat, cli
10
10
#Customer intent: As a customer, I want to create an ARO custer using the command line.
11
11
---
12
12
13
-
# Create an Azure Red Hat OpenShift 4.3 Cluster
13
+
# Create, access, and manage an Azure Red Hat OpenShift 4.3 Cluster
14
14
15
15
> [!IMPORTANT]
16
16
> Azure Red Hat OpenShift (ARO) 4.3 is offered in preview. Preview features are self-service and are provided as is and as available and are excluded from the service-level agreement (SLA) and limited warranty. Therefore, the features aren't meant for production use.
@@ -29,57 +29,101 @@ You'll need the following to create an Azure Red Hat OpenShift 4.3 cluster:
29
29
30
30
- The RP service principal and cluster service principal must each have the Contributor role on the cluster virtual network. If you have the "User Access Administrator" role on the virtual network, `az aro create` will set up the role assignments for you automatically.
31
31
32
-
##Installing the 'az aro' extension
33
-
The `az aro` extension allows you to create, access, and delete Azure Red Hat OpenShift (ARO) clusters directly from the command line using the Azure CLI. The `az aro` extension can be used with a subscription registered with the preview Azure Red Hat OpenShift 4.3 service.
32
+
### Install the 'az aro' extension
33
+
The `az aro` extension allows you to create, access, and delete Azure Red Hat OpenShift clusters directly from the command line using the Azure CLI.
34
34
35
-
1. Log in to Azure.
36
-
37
-
```bash
38
-
az login
39
-
```
40
-
41
-
2. Run the following command to install the `az aro` extension.
35
+
> [!Note]
36
+
> The `az aro` extension is currenty in preview. It may be changed or removed in a future release.
37
+
> To opt-in for the `az aro` extension preview you need to register the `Microsoft.RedHatOpenShift` resource provider.
38
+
>
39
+
> ```
40
+
> az provider register -n Microsoft.RedHatOpenShift --wait
41
+
> ```
42
42
43
-
```bash
44
-
az extension add --source https://arosvc.blob.core.windows.net/az-preview/aro-0.1.0-py2.py3-none-any.whl
45
-
```
46
-
47
-
3. Add the ARO extension path to your `az` configuration.
43
+
1. Log in to Azure.
48
44
49
-
```bash
50
-
cat >>~/.azure/config <<EOF
51
-
[extension]
52
-
dev_sources = $PWD/python
53
-
EOF
54
-
```
45
+
```
46
+
az login
47
+
```
55
48
56
-
4. Verify the ARO extension is registered.
49
+
2. Run the following command to install the `az aro` extension:
57
50
58
-
```console
59
-
az -v
51
+
```
52
+
az extension add --source https://arosvc.blob.core.windows.net/az-preview/aro-0.1.0-py2.py3-none-any.whl
53
+
```
60
54
61
-
Extensions:
62
-
aro 0.1.0 (dev) /path/to/rp/python/az/aro
63
-
Development extension sources:
64
-
/path/to/rp/python
65
-
```
55
+
3. Verify the ARO extension is registered.
66
56
67
-
5. To opt into the preview of Azure Red Hat OpenShift v4, register the
68
-
`Microsoft.RedHatOpenShift` resource provider.
57
+
```
58
+
az -v
59
+
...
60
+
Extensions:
61
+
aro 0.1.0
62
+
...
63
+
```
64
+
65
+
### Create a virtual network containing two empty subnets
66
+
67
+
Follow these steps to create a virtual network containing two empty subnets.
68
+
69
+
1. Set the following variables.
70
+
71
+
```
72
+
LOCATION=eastus #the location of your cluster
73
+
RESOURCEGROUP="v4-$LOCATION" #the name of the resource group where you want to create your cluster
74
+
CLUSTER=cluster #the name of your cluster
75
+
```
76
+
77
+
2. Create a resource group for your cluster.
78
+
79
+
```
80
+
az group create -g "$RESOURCEGROUP" -l $LOCATION
81
+
```
82
+
83
+
3. Create the virtual network.
84
+
85
+
```
86
+
az network vnet create \
87
+
-g "$RESOURCEGROUP" \
88
+
-n vnet \
89
+
--address-prefixes 10.0.0.0/9 \
90
+
>/dev/null
91
+
```
92
+
93
+
4. Add two empty subnets to your virtual network.
94
+
95
+
```
96
+
for subnet in "$CLUSTER-master" "$CLUSTER-worker"; do
5. Disable network policies for Private Link Service on your virtual network and subnets. This is a requirement for the ARO service to access and manage the cluster.
0 commit comments