Red Hat Openshift
Red Hat Openshift is a versatile platform for scalable application development, modernization, and deployment over Kubernetes, offering a complete service set for app delivery on your preferred infrastructure.
Using Port's Kubernetes Exporter, you can keep track of important Openshift resources across your different clusters and export the data to Port. You will use built in metadata from your Openshift resources and CRDs to create entities in Port and keep track of their state.
Get to know the basics of our Kubernetes exporter here!
Mapping Red Hat Openshift - Goals
While Red Hat Openshift provides great visibility when it comes to your Openshift (Kubernetes) environments, there are still some questions that remain about how your Openshift environment connects and interacts with the rest of your infrastructure, for example:
- Which cloud provider is the cluster running in?
- Which VPC is the cluster running in?
- Who is on-call for a given cluster?
- What are all the endpoints provided by all different Openshift clusters in a cloud region?
Importing your Openshift resources to Port makes it easy to create multiple tailored views for different use cases. For example, you can create a view that shows you how your Openshift cluster interacts with the rest of your infrastructure, or you can create a high-level view that allows management to understand the business value provided by your Openshift installations.
In this example you will map your Openshift clusters, their workloads and the Openshift routes which are exposed by your different clusters.
- Helm must be installed to use the chart. Please refer to Helm's documentation to get started;
jqcommand must installed;
yqcommand must installed;
kubectl/occommand must be installed;
- Have your Port credentials ready.
In this use-case, you will use a custom bash script which will assist you in the process of installing Port's K8s exporter.
For more information about the k8s exporter installation script click here!
The script will install the helm chart in the Openshift cluster which is currently in
To view the context name of the cluster the exporter will be installed on, run:
oc config current-context
Setting up your blueprints
Creating blueprints using the installation script
The installation script provides a convenient way to create your blueprints. Using the
CUSTOM_BP_PATH environment variable, you can fetch a pre-defined
blueprints.json to create your blueprints. For this use-case, you will use this file to define your blueprints. Do this by running:
blueprints.json file defines the following blueprints:
- Workload *;
- Openshift Route *.
Workloadis an abstraction of Kubernetes objects which create and manage pods. By creating this blueprint, you can avoid creating a dedicated blueprint per Workload type, all of which will likely look pretty similar. Here is the list of kubernetes objects
Openshift Routeis one of the most important Openshift resources, giving developers the capability to connect to their services, while the entire network layer is managed by the Openshift API, and providing a simple DNS record for accessability.
Installing the Kubernetes exporter using the script
CONFIG_YAML_URL parameter, you can define a custom
config.yaml to use when installing the exporter.
In this use-case you will be using this configuration file. To achieve this, run:
You can now run the installation script using the following code snippet:
curl -s https://raw.githubusercontent.com/port-labs/template-assets/main/kubernetes/install.sh | bash
You can now browse to your Port environment to see that your blueprints have been created, and your Kubernetes resources, including Openshift routes are being reported to Port using the freshly installed k8s exporter.