Académique Documents
Professionnel Documents
Culture Documents
The Microsoft Azure Red Hat OpenShift service enables you to deploy fully managed OpenShift clusters.
Azure Red Hat OpenShift extends Kubernetes. Running containers in production with Kubernetes requires
additional tools and resources, such as an image registry, storage management, networking solutions, and logging
and monitoring tools, all of which must be versioned and tested together. Building container-based applications
requires even more integration work with middleware, frameworks, databases, and CI/CD tools. Azure Red Hat
OpenShift combines all this into a single platform, bringing ease of operations to IT teams while giving application
teams what they need to execute.
Azure Red Hat OpenShift is jointly engineered, operated, and supported by Red Hat and Microsoft to provide an
integrated support experience. There are no virtual machines to operate, and no patching is required. Master,
infrastructure and application nodes are patched, updated, and monitored on your behalf by Red Hat and
Microsoft. Your Azure Red Hat OpenShift clusters are deployed into your Azure subscription and are included on
your Azure bill.
You can choose your own registry, networking, storage, and CI/CD solutions, or use the built-in solutions for
automated source code management, container and application builds, deployments, scaling, health management,
and more. Azure Red Hat OpenShift provides an integrated sign-on experience through Azure Active Directory.
To get started, complete the Create an Azure Red Hat OpenShift cluster tutorial.
Kubernetes certification
Azure Red Hat OpenShift service has been CNCF certified as Kubernetes conformant.
Next steps
Learn the prerequisites for Azure Red Hat OpenShift:
Set up your dev environment
Tutorial: Create an Azure Red Hat OpenShift cluster
7/9/2019 • 6 minutes to read • Edit Online
This tutorial is part one of a series. You'll learn how to create a Microsoft Azure Red Hat OpenShift cluster using
the Azure CLI, scale it, then delete it to clean up resources.
In part one of the series, you'll learn how to:
Create an Azure Red Hat OpenShift cluster
In this tutorial series you learn how to:
Create an Azure Red Hat OpenShift cluster
Scale an Azure Red Hat OpenShift cluster
Delete an Azure Red Hat OpenShift cluster
Prerequisites
IMPORTANT
This tutorial requires version 2.0.65 of the Azure CLI.
Before you can use Azure Red Hat OpenShift, you'll need to purchase a minimum of 4 Azure Red Hat OpenShift reserved
application nodes as described in Set up your Azure Red Hat OpenShift development environment.
az login
If you have access to multiple subscriptions, run az account set -s {subscription ID} replacing
{subscription ID} with the subscription you want to use.
Choose a location to create your cluster. For a list of azure regions that supports OpenShift on Azure, see
Supported Regions. For example: LOCATION=eastus .
LOCATION=<location>
Set APPID to the value you saved in step 5 of Create an Azure AD app registration.
APPID=<app ID value>
Set 'GROUPID' to the value you saved in step 10 of Create an Azure AD security group.
GROUPID=<group ID value>
Set SECRET to the value you saved in step 8 of Create a client secret.
SECRET=<secret value>
Set TENANT to the tenant ID value you saved in step 7 of Create a new tenant
TENANT=<tenant ID>
Create the resource group for the cluster. Run the following command from the same Bash shell that you used to
define the variables above:
First, get the identifier of the existing VNET. The identifier will be of the form:
/subscriptions/{subscription id}/resourceGroups/{resource group of
VNET}/providers/Microsoft.Network/virtualNetworks/{VNET name}
.
If you don't know the network name or the resource group the existing VNET belongs to, go to the Virtual
networks blade and click on your virtual network. The Virtual network page appears and will list the name of the
network and the resource group it belongs to.
Define a VNET_ID variable using the following CLI command in a BASH shell:
VNET_ID=$(az network vnet show -n {VNET name} -g {VNET resource group} --query id -o tsv)
For example: VNET_ID=$(az network vnet show -n MyVirtualNetwork -g MyResourceGroup --query id -o tsv
If you are peering your cluster to a virtual network, use the following command which adds the --vnet-peer
flag:
NOTE
If you get an error that the host name is not available, it may be because your cluster name is not unique. Try deleting your
original app registration and redoing the steps with a different cluster name in [Create a new app registration] (howto-aad-
app-configuration.md#create-a-new-app-registration), omitting the step of creating a new user and security group.
The sign in URL for your cluster will be followed by the publicHostName value. For example:
https://
https://openshift.xxxxxxxxxxxxxxxxxxxx.eastus.azmosa.io . You will use this URI in the next step as part of the app
registration redirect URI.
Sign in using the user name you created in step 3 of Create a new Azure Active Directory user.
A Permissions requested dialog will appear. Click Consent on behalf of your organization and then click
Accept.
You are now logged into the cluster console.
Learn more about using the OpenShift console to create and built images in the Red Hat OpenShift
documentation.
Next steps
In this part of the tutorial, you learned how to:
Create an Azure Red Hat OpenShift cluster
Advance to the next tutorial:
Scale an Azure Red Hat OpenShift cluster
Tutorial: Scale an Azure Red Hat OpenShift cluster
7/9/2019 • 2 minutes to read • Edit Online
This tutorial is part two of a series. You'll learn how to create a Microsoft Azure Red Hat OpenShift cluster using
the Azure CLI, scale it, then delete it to clean up resources.
In part two of the series, you learn how to:
Scale a Red Hat OpenShift cluster
In this tutorial series you learn how to:
Create an Azure Red Hat OpenShift cluster
Scale an Azure Red Hat OpenShift cluster
Delete an Azure Red Hat OpenShift cluster
Prerequisites
Before you begin this tutorial:
Create a cluster by following the Create an Azure Red Hat OpenShift cluster tutorial.
az login
If you have access to multiple subscriptions, run az account set -s {subscription ID} replacing
{subscription ID} with the subscription you want to use.
CLUSTER_NAME=yourclustername
Now let's scale the cluster to five nodes using the Azure CLI:
After a few minutes, az openshift scale will complete successfully and return a JSON document containing the
scaled cluster details.
Next steps
In this part of the tutorial, you learned how to:
Scale an Azure Red Hat OpenShift cluster
Advance to the next tutorial:
Delete an Azure Red Hat OpenShift cluster
Tutorial: Delete an Azure Red Hat OpenShift cluster
7/9/2019 • 2 minutes to read • Edit Online
This is the end of the tutorial. When you're finished testing the sample cluster, here's how to delete it and its
associated resources so you don't get charged for what you're not using.
In part three of the series, you learn how to:
Delete an Azure Red Hat OpenShift cluster
In this tutorial series you learn how to:
Create an Azure Red Hat OpenShift cluster
Scale an Azure Red Hat OpenShift cluster
Delete an Azure Red Hat OpenShift cluster
Prerequisites
Before you begin this tutorial:
Create a cluster by following the Create an Azure Red Hat OpenShift cluster tutorial.
az login
If you have access to multiple subscriptions, run az account set -s {subscription ID} replacing
{subscription ID} with the subscription you want to use.
CLUSTER_NAME=yourclustername
You'll be prompted whether you want to delete the cluster. After you confirm with y , it will take several minutes
to delete the cluster. When the command finishes, the entire Resource Group and all resources inside it, including
the cluster, will be deleted.
Deleting the resource group will delete all of the related resources that get created when you build an Azure Red
Hat OpenShift cluster.
Next steps
In this part of the tutorial, you learned how to:
Delete an Azure Red Hat OpenShift cluster
Learn more about using OpenShift with the official Red Hat OpenShift documentation
Set up your Azure Red Hat OpenShift dev
environment
7/9/2019 • 3 minutes to read • Edit Online
To build and run Microsoft Azure Red Hat OpenShift applications, you'll need to:
Purchase Azure virtual machine reserved instances.
Install version 2.0.65 (or higher) of the Azure CLI (or use the Azure Cloud Shell).
Register for the AROGA feature and associated resource providers.
Create an Azure Active Directory (Azure AD ) tenant.
Create an Azure AD application object.
Create an Azure AD user.
The following instructions will walk you through all of these prerequisites.
az --version
The first line of output will have the CLI version, for example azure-cli (2.0.65) .
Here are instructions for installing the Azure CLI if you require a new installation or an upgrade.
Alternately, you can use the Azure Cloud Shell. When using the Azure Cloud Shell, be sure to select the Bash
environment if you plan to follow along with the Create and manage an Azure Red Hat OpenShift cluster tutorial
series.
Next steps
You're now ready to use Azure Red Hat OpenShift!
Try the tutorial:
Create an Azure Red Hat OpenShift cluster
Create an Azure AD tenant for Azure Red Hat
OpenShift
5/29/2019 • 2 minutes to read • Edit Online
Microsoft Azure Red Hat OpenShift requires an Azure Active Directory (Azure AD ) tenant in which to create your
cluster. A tenant is a dedicated instance of Azure AD that an organization or app developer receives when they
create a relationship with Microsoft by signing up for Azure, Microsoft Intune, or Microsoft 365. Each Azure AD
tenant is distinct and separate from other Azure AD tenants and has its own work and school identities and app
registrations.
If you don't already have an Azure AD tenant, follow these instructions to create one.
8. Make note of the tenant ID so you can later specify where to create your Azure Red Hat OpenShift cluster.
In the portal, you should now see the Azure Active Directory overview blade for your new tenant. Select
Properties and copy the value for your Directory ID. We will refer to this value as TENANT in the Create an
Azure Red Hat OpenShift cluster tutorial.
Resources
Check out Azure Active Directory documentation for more info on Azure AD tenants.
Next steps
Learn how to create a service principal, generate a client secret and authentication callback URL, and create a new
Active Directory user for testing apps on your Azure Red Hat OpenShift cluster.
Create an Azure AD app object and user
Azure Active Directory integration for Azure Red Hat
OpenShift
7/9/2019 • 4 minutes to read • Edit Online
If you haven't already created an Azure Active Directory (Azure AD ) tenant, follow the directions in Create an
Azure AD tenant for Azure Red Hat OpenShift before continuing with these instructions.
Microsoft Azure Red Hat OpenShift needs permissions to perform tasks on behalf of your cluster. If your
organization doesn't already have an Azure AD user, Azure AD security group, or an Azure AD app registration to
use as the service principal, follow these instructions to create them.
If the wrong tenant is displayed, click your user name in the top right, then click Switch Directory, and select the
correct tenant from the All Directories list.
Create a new Azure Active Directory global administrator user to sign in to your Azure Red Hat OpenShift cluster.
1. Go to the Users-All users blade.
2. Click +New user to open the User pane.
3. Enter a Name for this user.
4. Create a User name based on the name of the tenant you created, with .onmicrosoft.com appended at the end.
For example, yourUserName@yourTenantName.onmicrosoft.com . Write down this user name. You'll need it to sign in
to your cluster.
5. Click Directory role to open the directory role pane, and select Global administrator and then click Ok at the
bottom of the pane.
6. In the User pane, click Show Password and record the temporary password. After you sign in the first time,
you'll be prompted to reset it.
7. At the bottom of the pane, click Create to create the user.
IMPORTANT
Synchronization of the cluster administrators group will work only after consent has been granted. You will see a green circle
with a checkmark and a message "Granted for Subscription Name" in the Admin consent required column.
For details on managing administrators and other roles, see Add or change Azure subscription administrators.
Resources
Applications and service principal objects in Azure Active Directory
Quickstart: Register an app with the Azure Active Directory v1.0 endpoint
Next steps
If you've met all the Azure Red Hat OpenShift prerequisites, you're ready to create your first cluster!
Try the tutorial:
Create an Azure Red Hat OpenShift cluster
Deploy a standalone Prometheus instance in an
Azure Red Hat OpenShift cluster
7/11/2019 • 4 minutes to read • Edit Online
This article describes how to configure a standalone Prometheus instance that uses service discovery in an Azure
Red Hat OpenShift cluster.
NOTE
Customer admin access to Azure Red Hat OpenShift cluster isn't required.
Target setup:
One project (prometheus-project), which contains Prometheus and Alertmanager.
Two projects (app-project1 and app-project2), which contain the applications to monitor.
You'll prepare some Prometheus config files locally. Create a new folder to store them. Config files are stored in the
cluster as secrets, in case secret tokens are added later to the cluster.
NOTE
To see if you're signed in to the correct cluster, run the oc whoami -c command.
oc new-project prometheus-project
oc new-project app-project1
oc new-project app-project2
NOTE
You can either use the -n or --namespace parameter, or select an active project by running the oc project command.
scrape_configs:
- job_name: prom-sd
scrape_interval: 30s
scrape_timeout: 10s
metrics_path: /metrics
scheme: http
kubernetes_sd_configs:
- api_server: null
role: endpoints
namespaces:
names:
- prometheus-project
- app-project1
- app-project2
The prometheus.yml file is a basic Prometheus configuration file. It sets the intervals and configures auto discovery
in three projects (prometheus-project, app-project1, app-project2). In the previous configuration file, the auto-
discovered endpoints are scraped over HTTP without authentication.
For more information about scraping endpoints, see Prometheus scape config.
global:
resolve_timeout: 5m
route:
group_wait: 30s
group_interval: 5m
repeat_interval: 12h
receiver: default
routes:
- match:
alertname: DeadMansSwitch
repeat_interval: 5m
receiver: deadmansswitch
receivers:
- name: default
- name: deadmansswitch
oc process -f https://raw.githubusercontent.com/openshift/origin/release-3.11/examples/prometheus/prometheus-
standalone.yaml | oc apply -f - -n prometheus-project
The prometheus-standalone.yaml file is an OpenShift template. It will create a Prometheus instance with oauth-
proxy in front of it and an Alertmanager instance, also secured with oauth-proxy. In this template, oauth-proxy is
configured to allow any user who can "get" the prometheus-project namespace (see the -openshift-sar flag).
NOTE
To verify if the prom StatefulSet has equal DESIRED and CURRENT number replicas, run the
oc get statefulset -n prometheus-project command. To check all resources in the project, run the
oc get all -n prometheus-project command.
To apply template to all the projects that you want allow service discovery, run the following commands:
To have Prometheus to gather metrics from itself, apply the permissions in prometheus-project.
NOTE
To verify that Role and RoleBinding were created correctly, run the oc get role and oc get rolebinding commands.
IMPORTANT
Remember to add the https:// prefix to beginning of the host name.
The Status > Service Discovery page will show 0/0 active targets.
To deploy an example application, which exposes basic Python metrics under the /metrics endpoint, run the
following commands:
The new applications should appear as valid targets on the Service Discovery page within 30 seconds after
deployment.
For more details, select Status > Targets.
NOTE
For every successfully scraped target, Prometheus adds a data point in the up metric. Select Prometheus in the upper-left
corner, enter up as the expression, and then select Execute.
Next steps
You can add custom Prometheus instrumentation to your applications. The Prometheus Client library, which
simplifies Prometheus metrics preparation, is ready for different programming languages.
For more information, see the following GitHub libraries:
Java
Python
Go
Ruby
Azure Red Hat OpenShift FAQ
6/13/2019 • 2 minutes to read • Edit Online
This article addresses frequently asked questions (FAQs) about Microsoft Azure Red Hat OpenShift.
Are master and infrastructure nodes abstracted away as they are with
Azure Kubernetes Service (AKS)?
No. All resources, including the cluster master, run in your customer subscription. These types of resources are put
in a read-only resource group.
This article details some common issues encountered while creating or managing Microsoft Azure Red Hat
OpenShift clusters.
Next steps
Try the Red Hat OpenShift Help Center for more on OpenShift troubleshooting.
Find answers to frequently asked questions about Azure Red Hat OpenShift.
Azure Red Hat OpenShift resources
5/29/2019 • 2 minutes to read • Edit Online
This topic lists the Azure regions and virtual machine sizes supported by the Microsoft Azure Red Hat OpenShift
service.
Azure regions
See Products available by region for a current list of regions where you can deploy Azure Red Hat OpenShift
clusters.
IMPORTANT
Each VM has a different number of drives that can be attached. This may not be as immediately clear as memory or CPU size.
Not all VM sizes are available in all regions. Even if the API supports the size you specify, you might get an error if the size is
not available in the region you specify. See Current list of supported VM sizes per region for more information.
Standard D4s v3 4 16 GB
Standard D8s v3 8 32 GB
Standard D16s v3 16 64 GB
- - -
Standard E4s v3 4 32 GB
Standard E8s v3 8 64 GB
- - -
Standard F8s v2 8 16 GB
SIZE VCPU RAM
Standard F16s v2 16 32 GB
Standard F32s v2 32 64 GB
Standard D4s v3 4 16 GB
Standard D8s v3 8 32 GB
Standard D16s v3 16 64 GB
Next steps
Try the Create a Azure Red Hat OpenShift cluster tutorial.