TelcoCloud Training

TelcoCloud Training Short & crisp courses for NFV/Telco-cloud technologies like OpenStack & Kubernetes in easy language.

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟭𝟬 -  "TLS & certificates in OpenShift" Imagine running multiple nodes in a Telco cluster an...
29/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟭𝟬 - "TLS & certificates in OpenShift"

Imagine running multiple nodes in a Telco cluster and tracking security certificate expiry for each one. The overhead of manually generating a security certificate and the private key in each cycle, and manually binding a TLS secret with each ingress resource to decrypt what is coming from outside the cluster.

All of this is automated with the built-in 𝗧𝗟𝗦 𝗿𝗼𝘂𝘁𝗶𝗻𝗴 𝗲𝗻𝗴𝗶𝗻𝗲, specifically the native Route API and the built-in 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗖𝗔 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿 in OpenShift.

1. The Internal Service CA Operator (Zero-Touch PKI). OpenShift automatically:

- Generates a valid internal X.509 certificate and private key.
- Mounts it into the target application pod.
- Continuously rotates the certificate before it expires- with zero external plugins.

2. In OpenShift, the "Route" resource natively defines three distinct TLS architectures directly in its specification:

- Edge: Decrypts at the cluster perimeter router.
- Passthrough: Encrypted traffic bypasses the router entirely and goes untouched straight to the pod.
- Re-encryption (Exclusive Pattern): Decrypts incoming traffic with an external public certificate at the edge, inspects it, and immediately re-encrypts it using an internal certificate before sending it across the internal network to the pod.

Standard Kubernetes Ingress has no native concept of re-encryption.

Using OpenShift, you are not dependent on external components (like NGINX), install a 3rd-party badge-making vendor (cert-manager), and manually program how TLS-bounded secrets inspect packets before they reach the destination




𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟵 -  "OpenShift builds" Assume you want to add a network automation script, an additional mi...
22/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟵 - "OpenShift builds"

Assume you want to add a network automation script, an additional microservice, and a sidecar container along with the CNF in the telco cloud.

How can you achieve that?

Well, in a normal K8s cluster, you have to build a Dockerfile that requires an external CI/CD pipeline (GitHub Actions, GitLab CI, Jenkins), build an image & then run it in the environment

In OpenShift, this whole process is built-in, using native Custom Resource Definitions (𝗕𝘂𝗶𝗹𝗱𝗖𝗼𝗻𝗳𝗶𝗴, 𝗕𝘂𝗶𝗹𝗱). Give OpenShift a Git URL; it compiles your code, creates the container, and deploys it.

OpenShift provides an end-to-end developer platform (PaaS) that handles both image creation and deployment, whereas standard Kubernetes strictly focuses on running pre-built container workloads.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟴 -  "oc login" In K8s, to get access to the cluster, you have to put in manual effort to ge...
19/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟴 - "oc login"

In K8s, to get access to the cluster, you have to put in manual effort to get a key from a 𝗹𝗼𝗰𝗸𝘀𝗺𝗶𝘁𝗵 (admin), but
in OpenShift, you walk up to the 𝗵𝗼𝘁𝗲𝗹 𝗳𝗿𝗼𝗻𝘁 𝗱𝗲𝘀𝗸 (the OpenShift OAuth server) and get an activated electronic keycard (session token).

Kubernetes has no native 'user' object or built-in authentication server; it relies on external tools (e.g., gcloud, kubelogin, or client certificates), so it never validates passwords or issues session tokens itself.

OpenShift builds an enterprise platform layer on top of Kubernetes. OC has native User, Group, and OAuth server APIs.

The "oc login" command is Red Hat OpenShift’s built-in, interactive CLI authentication mechanism that exchanges user credentials or an OAuth token directly for an API session, automatically updating your local ~/.kube/config file.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟳 -  "oc adm must-gather" Can you imagine the pain of manually collecting logs from several ...
15/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟳 - "oc adm must-gather"

Can you imagine the pain of manually collecting logs from several OpenShift clusters to troubleshoot latency-critical OpenShift deployments (like Open RAN and 5G Core)?

"oc adm must-gather" is OpenShift’s built-in "one-click black box recorder" for cluster debugging. When a cluster starts misbehaving, running this single command launches a temporary container that methodically queries cluster APIs, gathers logs, inspects node health, fetches resource definitions, and bundles everything into an organized archive ready for diagnosis or Red Hat Support.

When you run oc adm must-gather:

1. It spins up an ephemeral pod (by default, quay.io/openshift/origin-must-gather).

2. This pod executes automated collection scripts

3. It streams data back to your local machine, then destroys the temporary pod.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟲 -  "OpenShift ClusterOperators" There is a subtle difference between an Operator and a Clu...
08/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟲 - "OpenShift ClusterOperators"

There is a subtle difference between an Operator and a ClusterOperator, and many of us are still confused between them.

𝗔𝗻 𝗼𝗽𝗲𝗿𝗮𝘁𝗼𝗿 𝗶𝘀 𝗮 𝗴𝗲𝗻𝗲𝗿𝗶𝗰 𝗞𝟴𝘀 𝗰𝗼𝗻𝗰𝗲𝗽𝘁; it pairs custom definitions (CRDs) with custom controller loops to automate operational tasks (deploying, backing up, or scaling an application). Anyone can write an operator. It is like a 3rd-party plugin doing the LCM of a component like PostgreSQL, Kafka, Prometheus, Grafana, etc.

𝗢𝗻 𝘁𝗵𝗲 𝗼𝘁𝗵𝗲𝗿 𝗵𝗮𝗻𝗱, 𝗮 𝗖𝗹𝘂𝘀𝘁𝗲𝗿𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿 𝗶𝘀 𝗮𝗻 𝗲𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗰𝗼𝗻𝗰𝗲𝗽𝘁. It is a concrete, built-in OpenShift CRD shipped directly with OpenShift that manages the cluster platform itself, such as DNS, authentication, ingress, or the web console.

In telco environments, ClusterOperators automate deep bare-metal tuning, such as Real-Time kernels, SR-IOV, and PTP synchronization—required for high-performance 5G and RAN workloads.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟱 -  "OpenShift Authentication" Imagine a single OpenShift cluster hosts Cloud-Native Networ...
06/10/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟱 - "OpenShift Authentication"

Imagine a single OpenShift cluster hosts Cloud-Native Network Functions (CNFs) from multiple vendors (e.g., Ericsson, Nokia, Samsung). How will you achieve strict Multi-vendor isolation?

OR

In a large network with thousands of distributed Far-Edge / Single-Node OpenShift (SNO) sites, how will credentials be managed for Zero-Trust Identity Mapping without storing hardcoded static credentials locally?

OpenShift solves this gap by implementing a built-in 𝗢𝗔𝘂𝘁𝗵 𝘀𝗲𝗿𝘃𝗲𝗿 and first-class API resources to 𝗺𝗮𝗻𝗮𝗴𝗲 𝗶𝗱𝗲𝗻𝘁𝗶𝘁𝗶𝗲𝘀 natively.

In plain K8s, human users do not exist as cluster objects. K8s has ServiceAccounts for pods, but for humans, it relies entirely on external systems (like X.509 client certificates or external OIDC tokens) and simply trusts a string username passed in a header. 𝗬𝗼𝘂 𝗰𝗮𝗻𝗻𝗼𝘁 𝗿𝘂𝗻 '𝗸𝘂𝗯𝗲𝗰𝘁𝗹 𝗴𝗲𝘁 𝘂𝘀𝗲𝗿𝘀'

In OpenShift, you have cluster objects like Users, Groups, Identities, OAuthClient, and OAuthAccessToken that manage the whole user & auth management natively

If plain K8s is like an airport that doesn't maintain a profile or database record for you, then OpenShift is like a hotel that has its own membership database.



Don’t just chase a paycheck, infact chase the mastery that commands it. The money will fund your future, but the grind t...
03/10/2026

Don’t just chase a paycheck, infact chase the mastery that commands it.
The money will fund your future, but the grind that earned it will define who you are.


𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟰 -  "OpenShift imagestreamtags" Have you ever wondered how new container images get rolled ...
30/09/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟰 - "OpenShift imagestreamtags"

Have you ever wondered how new container images get rolled out in a TelcoCloud network?

Especially when you have 100 vDUs, 30 5G core functions, and 20 IMS nodes in the network, each having their specific container images hardcoded in the YAML manifests (either static files or Helm charts)

Well, this is possible via 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗜𝗺𝗮𝗴𝗲𝗦𝘁𝗿𝗲𝗮𝗺𝘀 𝗮𝗻𝗱 𝗜𝗺𝗮𝗴𝗲𝗦𝘁𝗿𝗲𝗮𝗺𝗧𝗮𝗴𝘀 that facilitate rapid and automated deployment of updated images to a vast and geographically distributed network of telco edge and core locations, reducing service downtime and improving network agility

Consider an OpenShift ImageStream as a smart browser bookmark pointing to company/manual:latest.
Your apps don't pull directly from a fixed URL; they look at the bookmark.

When the underlying document is updated in the registry, OpenShift detects the change, updates the bookmark's pointer, and can automatically notify your app to restart and pull the fresh content.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟯 -  "OpenShift MachineConfig and MachineConfigPool" Have you ever wondered, in a TelcoCloud...
28/09/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟯 - "OpenShift MachineConfig and MachineConfigPool"

Have you ever wondered, in a TelcoCloud cluster, how node-level real-time kernel parameters, hugepages, CPU pinning, and SR-IOV get tuned across thousands of remote edge cell sites without manual intervention?

This is possible via 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗺𝗮𝗰𝗵𝗶𝗻𝗲𝗖𝗼𝗻𝗳𝗶𝗴𝘀, which let you manage the underlying Linux operating system (RHCOS) of your nodes using the same declarative YAML approach you use for containers.

In OpenShift, think of it as a centrally managed fleet of corporate laptops managed by corporate IT policies.
However, in K8s, everyone has a DIY PC setup, and you have to tune these changes manually.

MachineConfig is a declarative definition of the host OS state. It tells the node what files to write (e.g., in /etc/), what systemd services to run, which kernel modules or arguments to enable, and what SSH keys or container runtime settings to apply on each worker node or a pool of nodes.



𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟮 -  "OpenShift Routes" In K8s, setting up an ingress is a DIY route setup with an office in...
24/09/2026

𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟮 - "OpenShift Routes"

In K8s, setting up an ingress is a DIY route setup with an office intercom (internal svc) system.
While in OpenShift, it is like pressing a single button to hire a dedicated concierge and install an illuminated front door with a custom business sign.

An OpenShift Route is an out-of-the-box mechanism that exposes an internal application running in your cluster to the outside world using a public, human-readable URL

This is possible via a single 'oc expose svc' command, and there is no equivalent of 'oc expose' in plain K8s

This single command creates a custom OpenShift API object called a Route. The built-in OpenShift HAProxy router detects it automatically, maps the domain to your internal service, and immediately begins routing incoming HTTP/HTTPS traffic.

In telco cloud deployments, OpenShift Routes and oc expose provide instant, automated, and secure North-South ingress for management plane and OSS/BSS APIs, removing the operational overhead of third-party ingress controllers at distributed edge sites.


Address

133, Data Colony, Airport Road
Bhopal
462030

Alerts

Be the first to know and let us send you an email when TelcoCloud Training posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to TelcoCloud Training:

Shortcuts

Share

Nearby computer & electronics services