Azure Red Hat OpenShift 4.x— The White bird

A charming white bird is bringing additional freedom to end users.

Read-on to find out more!

Azure Red Hat OpenShift 4.x —New Logo!

What’s new?

  • Full Cluster-Admin rights,
  • No lock-in to Azure AD, nor to Virtual Networks,
  • New Dashboard experience,
  • Hybrid Cluster Management console, Cost Management,
  • An additional set of security features,
  • Network Isolation with Azure Private Link,
  • Private Cluster through the usage of ingress endpoints,
  • Multi-Availability zones, auto-scalable clusters,
  • Over-The-Air Upgrades,
  • Certified Operators such as Istio, Tekton and many more.
OpenShift 4 — Operators

First, What about the Freedom?

oc adm top nodes
oc adm top nodes --selector=""

We still can not SSH to master nodes, but do we really need that?

But wait! Let’s discuss first how to create an ARO cluster.

Cluster Provisioning

Following this link you’ll get a Terraform ready to use for ARO 4.x cluster provisioning.

#AZ ARO Help:
az aro -h
#Deploy Command:
az aro create -g <ResourceGroup> -n <ClusterName> --domain <Domain>
  • Bring his own Virtual Network and took full ownership of it,
  • Tag the ARO resources deployed,
  • Apply the desired Naming Convention on all ARO Resource Groups,
  • Bring his own Identity Provider, which can be set to GitHub, Azure AD or others.

Operators

Cluster Scalability

oc get machinesets -n openshift-machine-api
oc scale --replicas=2 machineset <machineset> \
-n openshift-machine-api

Private Cluster

A single pane of glass

Dashboard

Cluster Management

Cost Management

Security

Private Link

Authentication & Authorization

Azure AD Group synchro

And Much more!

Serverless / Knative

KNative — Kubernetes Native

Service Mesh

To know more about Service Mesh, please check my previous blog post.

Argo CD

API Explorer

Drawbacks?

  • Even that Version 4.5 is available within the Stable channel, Microsoft still limits their support to ARO v4.4 only. Final customers are not allowed to upgrade/patch the cluster to any release manually.
  • The Service Level Agreement is not clear yet and not measurable. No details provided around availability, response-time or quality is provided by Microsoft.
  • ARO Documentation is not exhaustive and complete.
  • Other points to notice with ARO 4.x is that there are still no possibilities to switch from the native SDN provider “OpenShiftSDN” to “Kuryr”, “OVNKubernetes”, or others. Red Hat is still restricting its support to the OpenShiftSDN network provider, limiting the support for Microsoft.
  • Any modifications to the cluster components can bring the cluster to unsupported mode. Those modifications are highlighted in the following document yet so generic. So, it’s advised to be aware of them.

Could you please read the support policy below carefully?

Conclusion

--

--

--

Is a Cloud-Native enthusiast with 12 plus years of experience. He’s continuously immersing himself in the latest technology trends & projects.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

How to Follow the Dependency Inversion Principle in NestJS and Angular

Nest and Angular logos

Configuring IPTABLES to work with AWS hosts (like *.crashlytics.com)

Spinning the wheel in Flutter

Is Engineering Manager an expendable role?

Getting started with git — the practical way

Image Processing API: Resize an Image with Java

Launching of wordpress and mysql with bastion os for updating mysql

How to use Gutenberg editor: Exploring blocks

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Aymen Abdelwahed

Aymen Abdelwahed

Is a Cloud-Native enthusiast with 12 plus years of experience. He’s continuously immersing himself in the latest technology trends & projects.

More from Medium

Access Secrets from Azure Key Vault in Azure Kubernetes Service

How to Use WAF of Application Gateway With AKS

Kubernetes Pattern: How to Deploy an Asp.Net Core 3.1 Web API on Azure Kubernetes Cluster

How to Use Functions and Pipelines in Helm