OKD 4.8 Documentation

OKD installation overview: You can install OKD on installer-provisioned or user-provisioned infrastructure. The OKD installation program provides the flexibility to deploy OKD on a range of different platforms.

Install a cluster on AWS: You have many installation options when you deploy a cluster on Amazon Web Services (AWS). You can deploy clusters with default settings or custom AWS settings. You can also deploy a cluster on AWS infrastructure that you provisioned yourself. You can modify the provided AWS CloudFormation templates to meet your needs.

Install a cluster on Azure: You can deploy clusters with default settings, custom Azure settings, or custom networking settings in Microsoft Azure. You can also provision OKD into an Azure Virtual Network or use Azure Resource Manager Templates to provision your own infrastructure.

Install a cluster on GCP: You can deploy clusters with default settings or custom GCP settings on Google Cloud Platform (GCP). You can also perform a GCP installation where you provision your own infrastructure.

Install a cluster on VMware vSphere: You can install OKD on supported versions of vSphere.

Install an installer-provisioned cluster on bare metal: You can install OKD on bare metal with an installer-provisioned architecture.

Install a user-provisioned cluster on bare metal: If none of the available platform and cloud provider deployment options meet your needs, you can install OKD on user-provisioned bare metal infrastructure.

Install a cluster on Red Hat OpenStack Platform (RHOSP): You can install a cluster on RHOSP with customizations.

Install a cluster on oVirt: You can deploy clusters on oVirt with a quick install or an install with customizations.

Install a cluster in a restricted network: If your cluster that uses user-provisioned infrastructure on AWS, GCP, or bare metal does not have full access to the internet, then mirror the OKD installation images and install a cluster in a restricted network.

Install a cluster in an existing network: If you use an existing Virtual Private Cloud (VPC) in AWS or GCP or an existing VNet on Azure, you can install a cluster.

Install a private cluster: If your cluster does not require external internet access, you can install a private cluster on AWS, Azure, or GCP. Internet access is still required to access the cloud APIs and installation media.

Check installation logs: Access installation logs to evaluate issues that occur during OKD 4.8 installation.

Access OKD: Use credentials output at the end of the installation process to log in to the OKD cluster from the command line or web console.

Install Red Hat OpenShift Container Storage: You can install Red Hat OpenShift Container Storage as an Operator to provide highly integrated and simplified persistent storage management for containers.

Understand OKD development: Learn the different types of containerized applications, from simple containers to advanced Kubernetes deployments and Operators.

Work with projects: Create projects from the OKD web console or OpenShift CLI (oc) to organize and share the software you develop.

Work with applications:

Use the developer CLI tool (odo): The odo CLI tool lets developers create single or multi-component applications easily and automates deployment, build, and service route configurations. It abstracts complex Kubernetes and OKD concepts, allowing you to focus on developing your applications.

Create CI/CD Pipelines: Pipelines are serverless, cloud-native, continuous integration and continuous deployment systems that run in isolated containers. They use standard Tekton custom resources to automate deployments and are designed for decentralized teams that work on microservices-based architecture.

Deploy Helm charts: Helm 3 is a package manager that helps developers define, install, and update application packages on Kubernetes. A Helm chart is a packaging format that describes an application that can be deployed using the Helm CLI.

Understand image builds: Choose from different build strategies (Docker, s2i, custom, and pipeline) that can include different kinds of source materials (from places like Git repositories, local binary inputs, and external artifacts). Then, follow examples of build types from basic builds to advanced builds.

Create container images: A container image is the most basic building block in OKD (and Kubernetes) applications. Defining image streams lets you gather multiple versions of an image in one place as you continue its development. s2i containers let you insert your source code into a base container that is set up to run code of a particular type, such as Ruby, Node.js, or Python.

Create deployments: Use Deployment and DeploymentConfig objects to exert fine-grained management over applications. Manage deployments using the Workloads page or OpenShift CLI (oc). Learn rolling, recreate, and custom deployment strategies.

Create templates: Use existing templates or create your own templates that describe how an application is built or deployed. A template can combine images with descriptions, parameters, replicas, exposed ports and other content that defines how an application can be run or built.

Understand Operators: Operators are the preferred method for creating on-cluster applications for OKD 4.8. Learn about the Operator Framework and how to deploy applications using installed Operators into your projects.

Develop Operators: Operators are the preferred method for creating on-cluster applications for OKD 4.8. Learn the workflow for building, testing, and deploying Operators. Then, create your own Operators based on Ansible or Helm, or configure built-in Prometheus monitoring using the Operator SDK.

REST API reference: Learn about OKD application programming interface endpoints.

Understand OKD management: Learn about components of the OKD 4.8 control plane. See how OKD control plane and worker nodes are managed and updated through the Machine API and Operators.