Usage of oc and kubectl commands. creationTimestamp, generation, etc. The output shows configuration information associated with the dev-frontend context: Now suppose you want to work for a while in the test cluster. The kubeconfig file can contain clusters, users, and contexts. This page shows how to configure access to multiple clusters by using configuration files. If the KUBECONFIG environment variable doesn't exist, The file is specific to a cluster and is created during OpenShift Container Platform installation. create-kubeconfig OCI CLI Command Reference 3.29.4 - Oracle If the namespace does not exist inside Kubernetes, the commands will fail and display the default Kubernetes message for a nonexistent namespace. Sets a context entry in the CLI config file. The oc login command is used to authenticate against the API server. Usually, the kubectl or oc commands use the kubeconfig file. The kubeconfig file contains information about the cluster that is used by the CLI to connect a client to the correct cluster and API server. Logging Into a Kubernetes Cluster With Kubectl - Software Blog in a variety of ways. Red Hat OpenShift and Kubernetes what's the difference? You can log in to your cluster as a default system user by exporting the cluster kubeconfig file. Overriding role arn in existing kubeconfig from aws cli/kubectl cli The oc registry login command is failing during setup of mirror registry: Raw $ oc registry login --to ./nowhere.json --registry nowhere:5000 --auth-basic=nothing:nothing error: Missing or incomplete configuration info. k8skubeconfigkubeconfig kubectl . kubeconfigkubectlkubeconfigAPI, kubectl$HOME/.kubeconfigKUBECONFIG--kubeconfigkubeconfig, kubeconfig, , kubeconfigcontext, kubeconfigcontextcontext3clusternamespaceuserkubectlcurrent context, KUBECONFIGkubeconfigLinuxMacWindowsKUBECONFIGKUBECONFIGkubectlkubeconfig$HOME/.kube/config, KUBECONFIGkubectlKUBECONFIG, 1kubeconfigkubeconfig, kubectlkubeconfig, --kubeconfig1, KUBECONFIGKUBECONFIG, KUBECONFIGKUBECONFIG, kubeconfig$HOME/.kube/config, context, context12, , 1, , kubeconfigkubeconfig$HOME/.kube/config, kubeconfigproxy-urlkubectl. ubuntu - oc cluster up can't start kube-apiserver due to missing However, you can create a kubeconfigby executing some kubectl config commands. rules as cluster information, except allow only one authentication In this case, there is only a single user, named minikube. A context consists of user authentication and OpenShift Container Platform server information associated with a nickname. We appreciate your interest in having Red Hat content localized to your language. Extract the OpenShift payloads (aka files, assets, etc.) Produce errors for files with content that cannot be deserialized. kubectlkubeconfig, KUBECONFIGkubeconfigLinux, MacOS(Windows). kind: Config Red Hat JBoss Enterprise Application Platform, Red Hat Advanced Cluster Security for Kubernetes, Red Hat Advanced Cluster Management for Kubernetes, Red Hat OpenShift Container Platform (RHOCP). Go to your config-exercise directory. A running kubelet might authenticate using certificates. Keep your systems secure with Red Hat's specialized responses to security vulnerabilities. Via the command-line flag --config 2. nickname already exists, the specified information is merged in. In order to view the different releases and some information, the following snippet can be used (in this example the stable-4.2 channel is used): This can be wrapped in a handy script such as: For creating a Kubeconfig file from a given credentials we can run the following commands: If you want to merge multiple kubeconfig files you can run the following commands: Ensure there arent duplicated entries (Context Names or User Names), There are duplicated users and names so we need to edit the kubeconfig files and assign a correct value for each kubeconfig file, Now were ready to merge the three kubeconfigs into a single one, Now you can export the new Kubeconfig and use --context [kube1|kube2|kube3] or oc config use [kube1|kube2|kube3] to work with the different clusters. might not be cluster information. Run multiple operations with the same kubeconfig file that do project/ns events Actual results: kubeconfig file becomes corrupt. Command line options take precedence over config file values. The default location of the kubeconfig file is ~/.kube/config. After you are logged in, you can use the oc status or oc project command to verify your current working environment: You can run the oc login command again and supply the required information during the interactive process, to log in using any other combination of user credentials and cluster details. kubectl k8sAPI. A CLI configuration file allows you to configure different profiles, or contexts, for use with the CLI tools overview. suggest an improvement. I've not found a good way to login to multiple Kubernetes clusters (well, actually I have: using the OpenShift oc command-line client, which has a login command which basically automates all of the below) out of the box, so here's a quick intro to the kubectl . Do not merge. EX180 OC login issue - Red Hat Learning Community Configure Access to Multiple Clusters. Example: Print the contents of the ruby-1-ca ConfigMap to stdout. # Storing passwords in Kubernetes client config is risky. Usually, the kubectl or oc commands use the kubeconfig file. Determine the context to use based on the first hit in this chain: An empty context is allowed at this point. contexts: # A better alternative would be to use a credential plugin, # See https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins, API access to authentication information for a client, Update docs for kubectl auth whoami (1b66978934), Append $HOME/.kube/config to your KUBECONFIG environment variable, Check the subject represented by the kubeconfig. dev-ramp-up context from the config-demo-2 file and the three contexts from of certificate files in your environment. to the test cluster requires authentication by username and password. under a convenient name. ), Get the repositories and commits used for the OpenShift release images, Get pull specs for all the release images, Get the pull spec for one components image, Get commit URLs for all the release components, Get the list of images included in a release, Get a diff from an image between different OpenShift versions, View different channels and releases information, Show logs for all containers running in the same pod, Avoid the managed fields and other metadata output, https://github.com/openshift/multus-cni/commits/0ad77469f3dbe7fa0a9cf5df5cd2a7fd3f099d2a, https://github.com/kubernetes/kubernetes/issues/90066#issuecomment-716206402. by Determine the cluster and user. certificate files; in that case you need to add the suffix -data to the keys, for example, Valid command line options are: For any information that is still missing, default values are used and prompts are given for additional information. Please login or point to an existing, complete config file: 1. Burn rates help you predict whether your downtime is too high or risks exceeding your service-level objective. In your config-exercise directory, enter: Return your KUBECONFIG environment variable to its original value. Removing the kubeadmin user | Authentication | OpenShift Container kubeconfig is the default way to authenticate to a Kubernetes cluster. alice-project/openshift1.example.com:8443/alice, joe-project/openshift1.example.com:8443/alice, xZHd2piv5_9vQrg-SKXRJ2Dsl9SceNJdhNTljEKTb8k, oc status You can change the context manually by editing the kubeconfig file, but this can lead to errors. The name of the file that will be updated with response data, or '-' to write to STDOUT. in the list. The context name is arbitrary, but the user and cluster should be predefined inside the kubeconfig file. kubeconfig - oc commands: error: You must be logged in to the server error: x509 certificate signed by unknown authority when logging in variable or by setting the Cluster info DUMP. Via https://github.com/kubernetes/kubernetes/issues/90066#issuecomment-716206402. Take a look inside Kubernetes and find the role-based access control (RBAC) objects that manage this authentication: This clusterrolebinding connects the cluster-admin clusterrole to the system:masters group. By default, kubectl looks for a file named config in the $HOME/.kube directory. Engage with our Red Hat Product Security team, access security updates, and ensure your environments are not exposed to any known security vulnerabilities. $ oc extract configmap/ruby-1-ca --to=-. Script OpenShift Container Platform operations. If any cluster information attributes exist from the merged kubeconfig files, use them. Checking if required ports are available . Importing an OpenShift cluster - IBM Use kubeconfig files to organize information about clusters, users, namespaces, and authentication mechanisms. To inspect an X.509 certificate, use the openssl command. Configure Access to Multiple Clusters | Kubernetes Determine the cluster and user based on the first hit in this chain, After you define an identity provider and create a new cluster-admin user, you can remove the kubeadmin to improve cluster security. In the development cluster, your frontend developers work in a namespace called frontend, Hector Vido (Red Hat). OpenShift - Log into OpenShift using the oc login command Example: Download the contents of the ruby-1-ca ConfigMap to the current directory. Otherwise, if the KUBECONFIG environment variable is set, use it as a For a list of available commands and options, see the kubectl documentation. Last modified April 04, 2023 at 6:56 PM PST: Installing Kubernetes with deployment tools, Customizing components with the kubeadm API, Creating Highly Available Clusters with kubeadm, Set up a High Availability etcd Cluster with kubeadm, Configuring each kubelet in your cluster using kubeadm, Communication between Nodes and the Control Plane, Resource Management for Pods and Containers, Organizing Cluster Access Using kubeconfig Files, Guide for Running Windows Containers in Kubernetes, Compute, Storage, and Networking Extensions, Changing the Container Runtime on a Node from Docker Engine to containerd, Migrate Docker Engine nodes from dockershim to cri-dockerd, Find Out What Container Runtime is Used on a Node, Troubleshooting CNI plugin-related errors, Check whether dockershim removal affects you, Migrating telemetry and security agents from dockershim, Configure Default Memory Requests and Limits for a Namespace, Configure Default CPU Requests and Limits for a Namespace, Configure Minimum and Maximum Memory Constraints for a Namespace, Configure Minimum and Maximum CPU Constraints for a Namespace, Configure Memory and CPU Quotas for a Namespace, Switching from Polling to CRI Event-based Updates to Container Status, Change the Reclaim Policy of a PersistentVolume, Configure a kubelet image credential provider, Control CPU Management Policies on the Node, Control Topology Management Policies on a node, Guaranteed Scheduling For Critical Add-On Pods, Migrate Replicated Control Plane To Use Cloud Controller Manager, Reserve Compute Resources for System Daemons, Running Kubernetes Node Components as a Non-root User, Using NodeLocal DNSCache in Kubernetes Clusters, Assign Memory Resources to Containers and Pods, Assign CPU Resources to Containers and Pods, Configure GMSA for Windows Pods and containers, Resize CPU and Memory Resources assigned to Containers, Configure RunAsUserName for Windows pods and containers, Configure a Pod to Use a Volume for Storage, Configure a Pod to Use a PersistentVolume for Storage, Configure a Pod to Use a Projected Volume for Storage, Configure a Security Context for a Pod or Container, Configure Liveness, Readiness and Startup Probes, Attach Handlers to Container Lifecycle Events, Share Process Namespace between Containers in a Pod, Translate a Docker Compose File to Kubernetes Resources, Enforce Pod Security Standards by Configuring the Built-in Admission Controller, Enforce Pod Security Standards with Namespace Labels, Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller, Developing and debugging services locally using telepresence, Declarative Management of Kubernetes Objects Using Configuration Files, Declarative Management of Kubernetes Objects Using Kustomize, Managing Kubernetes Objects Using Imperative Commands, Imperative Management of Kubernetes Objects Using Configuration Files, Update API Objects in Place Using kubectl patch, Managing Secrets using Configuration File, Define a Command and Arguments for a Container, Define Environment Variables for a Container, Expose Pod Information to Containers Through Environment Variables, Expose Pod Information to Containers Through Files, Distribute Credentials Securely Using Secrets, Run a Stateless Application Using a Deployment, Run a Single-Instance Stateful Application, Specifying a Disruption Budget for your Application, Coarse Parallel Processing Using a Work Queue, Fine Parallel Processing Using a Work Queue, Indexed Job for Parallel Processing with Static Work Assignment, Handling retriable and non-retriable pod failures with Pod failure policy, Deploy and Access the Kubernetes Dashboard, Use Port Forwarding to Access Applications in a Cluster, Use a Service to Access an Application in a Cluster, Connect a Frontend to a Backend Using Services, List All Container Images Running in a Cluster, Set up Ingress on Minikube with the NGINX Ingress Controller, Communicate Between Containers in the Same Pod Using a Shared Volume, Extend the Kubernetes API with CustomResourceDefinitions, Use an HTTP Proxy to Access the Kubernetes API, Use a SOCKS5 Proxy to Access the Kubernetes API, Configure Certificate Rotation for the Kubelet, Adding entries to Pod /etc/hosts with HostAliases, Externalizing config using MicroProfile, ConfigMaps and Secrets, Apply Pod Security Standards at the Cluster Level, Apply Pod Security Standards at the Namespace Level, Restrict a Container's Access to Resources with AppArmor, Restrict a Container's Syscalls with seccomp, Exposing an External IP Address to Access an Application in a Cluster, Example: Deploying PHP Guestbook application with Redis, Example: Deploying WordPress and MySQL with Persistent Volumes, Example: Deploying Cassandra with a StatefulSet, Running ZooKeeper, A Distributed System Coordinator, Explore Termination Behavior for Pods And Their Endpoints, Certificates and Certificate Signing Requests, Mapping PodSecurityPolicies to Pod Security Standards, Well-Known Labels, Annotations and Taints, ValidatingAdmissionPolicyBindingList v1alpha1, Kubernetes Security and Disclosure Information, Articles on dockershim Removal and on Using CRI-compatible Runtimes, Event Rate Limit Configuration (v1alpha1), kube-apiserver Encryption Configuration (v1), kube-controller-manager Configuration (v1alpha1), Contributing to the Upstream Kubernetes Code, Generating Reference Documentation for the Kubernetes API, Generating Reference Documentation for kubectl Commands, Generating Reference Pages for Kubernetes Components and Tools. . The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. insecure-skip-tls-verify: true The is the new value being set. kubernetes, TTL(TTL Controller for Finished Resources), (Dynamic Volume Provisioning), Compute, Storage, and Networking Extensions, Changing the Container Runtime on a Node from Docker Engine to containerd, Migrate Docker Engine nodes from dockershim to cri-dockerd, Troubleshooting CNI plugin-related errors, Configure Default CPU Requests and Limits for a Namespace, Configure Minimum and Maximum CPU Constraints for a Namespace, Configure Memory and CPU Quotas for a Namespace, Switching from Polling to CRI Event-based Updates to Container Status, Change the Reclaim Policy of a PersistentVolume, Configure a kubelet image credential provider, Control CPU Management Policies on the Node, Guaranteed Scheduling For Critical Add-On Pods, Migrate Replicated Control Plane To Use Cloud Controller Manager, Reserve Compute Resources for System Daemons, Running Kubernetes Node Components as a Non-root User, Configure GMSA for Windows Pods and containers, Resize CPU and Memory Resources assigned to Containers, Configure RunAsUserName for Windows pods and containers, Configure a Pod to Use a PersistentVolume for Storage, Liveness ProbeReadiness ProbeStartup Probe, Translate a Docker Compose File to Kubernetes Resources, Enforce Pod Security Standards by Configuring the Built-in Admission Controller, Enforce Pod Security Standards with Namespace Labels, Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller, Declarative Management of Kubernetes Objects Using Configuration Files, Declarative Management of Kubernetes Objects Using Kustomize, Managing Kubernetes Objects Using Imperative Commands, Imperative Management of Kubernetes Objects Using Configuration Files, Update API Objects in Place Using kubectl patch, Define a Command and Arguments for a Container, Expose Pod Information to Containers Through Files, Specifying a Disruption Budget for your Application, Coarse Parallel Processing Using a Work Queue, Fine Parallel Processing Using a Work Queue, Handling retriable and non-retriable pod failures with Pod failure policy, Use Port Forwarding to Access Applications in a Cluster, MinikubeNGINX IngressIngress, Extend the Kubernetes API with CustomResourceDefinitions, Use an HTTP Proxy to Access the Kubernetes API, Use a SOCKS5 Proxy to Access the Kubernetes API, HostAliasesPod/etc/hosts, Externalizing config using MicroProfile, ConfigMaps and Secrets, : PHP / Redis, Restrict a Container's Access to Resources with AppArmor, Restrict a Container's Syscalls with seccomp, : Persistent VolumeWordpressMySQL, Running ZooKeeper, A Distributed System Coordinator, Certificates and Certificate Signing Requests, Mapping PodSecurityPolicies to Pod Security Standards, Well-Known Labels, Annotations and Taints, ValidatingAdmissionPolicyBindingList v1alpha1, Kubernetes Security and Disclosure Information, Articles on dockershim Removal and on Using CRI-compatible Runtimes, Event Rate Limit Configuration (v1alpha1), kube-apiserver Encryption Configuration (v1), kube-controller-manager Configuration (v1alpha1), Contributing to the Upstream Kubernetes Code, Generating Reference Documentation for the Kubernetes API, Generating Reference Documentation for kubectl Commands, Generating Reference Pages for Kubernetes Components and Tools, [ja]Fix invalid Japanese words (6c40749966), contextcontext, kubeconfig. If you have a specific, answerable question about how to use Kubernetes, ask it on [default: ~/.kube/config] Provide input to this command as a JSON document from a file using the file://path-to/file syntax. required. Access developers work in the default namespace, or they create auxiliary namespaces as they Chapter 3. Logging in to the cluster - Red Hat Customer Portal OpenShift tips: How to recover a lost kubeadmin password for an OpenShift 4 cluster, How to fix Kubernetes namespaces stuck in the terminating state, Deploy an application in Red Hat OpenShift on your laptop, Enabling Kubernetes self-service the operator way, How API burn rate alerts are calculated in Red Hat OpenShift, difference between Red Hat OpenShift and Kubernetes, A practical introduction to container terminology, Interactive course: Getting started with OpenShift. You can run the oc login command again and supply the required information during the interactive process, to log in using any other combination of user credentials and cluster details. After your clusters, users, and contexts are defined in oc login -u kubeadmin -p <kubeadmin_password> User can starting using oc commands once logged into the cluster. directory. Access to the development cluster requires authentication by certificate. The oc config command includes a number of helpful sub-commands for this purpose: Sets a cluster entry in the CLI config file. All oc commands throws the following error: A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more. The context to use is determined based on the first match in the following flow: The current-context value from the CLI config file. the current context, use the --minify flag. report a problem Kubernetes components like kubelet, kube-controller-manager, or kubectl use the kubeconfig file to interact with the Kubernetes API. : StorageClass object doesnt have a condition field, so instead, wait for the object to be created: Powered by Hugo. for the pathnames of the certificate files. kubeconfig | Kubernetes At this point, there might or users: If you do not already have a Apply all manifests inside a folder. At this point, there might or might not be a context. the current context to communicate with the cluster. Learn how operators can serve as governance tools in a multitenant setting. OpenShift Container Platformoc login - Qiita In this case, there is only one, named minikube. Just in case you need it, here's how to recover a lost or forgotten kubeadmin password. familiarize yourself with the contents of these files. The user and cluster to use is determined. The file contents may differ in some cases, but the principle is the same. 1 Answer Sorted by: 0 I had the same problem and it was caused by an old certificate that was expired and had nothing to do (VMware one) with Openshift. kubectlkubernetes(k8s)APIkubectlDocumentkubectlDocument, kubectlk8sAPI, k8skubeconfigkubeconfigkubectlkubeconfigkubeconfigkubeconfig, kubeconfigkubectl config view, developerdevelopmentexperimenterexperiment, contextscontextnamespace. cluster, you can create one by using It is possible to switch between them with kubectl config use-context. About the CLI With the OpenShift Container Platform command-line interface (CLI), you can create applications and manage OpenShift Container Platform projects from a terminal. What is a kubeconfig file? | Enable Sysadmin Logging in to your cluster from the command-line interface - IBM For step-by-step instructions on creating and specifying kubeconfig files, see As more authentication and connection details are provided to the CLI, either automatically during an oc login operation or by manually configuring CLI profiles, the updated information is stored in the configuration file: The CLI can support multiple configuration files which are loaded at runtime and merged together along with any override options specified from the command line. namespace: default the credentials of the user listed in the dev-frontend context. GitHub Closed philips commented on Jul 13, 2018 Minishift version: minishift v1.21.0+a8c8b37 OS: macOS Hypervisor: VirtualBox minishift start --vm-driver virtualbox See start message with login instructions. report a problem Create the KUBECONFIG file. token: ns7yVhuRNpDM9cgzfhhxQ7bM5s7N2ZVrkZepSRf4LC0, Learn more about OpenShift Container Platform, OpenShift Container Platform 4.7 release notes, Selecting an installation method and preparing a cluster, Mirroring images for a disconnected installation, Installing a cluster on AWS with customizations, Installing a cluster on AWS with network customizations, Installing a cluster on AWS in a restricted network, Installing a cluster on AWS into an existing VPC, Installing a cluster on AWS into a government or secret region, Installing a cluster on AWS using CloudFormation templates, Installing a cluster on AWS in a restricted network with user-provisioned infrastructure, Installing a cluster on Azure with customizations, Installing a cluster on Azure with network customizations, Installing a cluster on Azure into an existing VNet, Installing a cluster on Azure into a government region, Installing a cluster on Azure using ARM templates, Installing a cluster on GCP with customizations, Installing a cluster on GCP with network customizations, Installing a cluster on GCP in a restricted network, Installing a cluster on GCP into an existing VPC, Installing a cluster on GCP using Deployment Manager templates, Installing a cluster into a shared VPC on GCP using Deployment Manager templates, Installing a cluster on GCP in a restricted network with user-provisioned infrastructure, Installing a cluster on bare metal with network customizations, Restricted network bare metal installation, Setting up the environment for an OpenShift installation, Installing a cluster with z/VM on IBM Z and LinuxONE, Restricted network IBM Z installation with z/VM, Installing a cluster with RHEL KVM on IBM Z and LinuxONE, Restricted network IBM Z installation with RHEL KVM, Installing a cluster on IBM Power Systems, Restricted network IBM Power Systems installation, Installing a cluster on OpenStack with customizations, Installing a cluster on OpenStack with Kuryr, Installing a cluster on OpenStack on your own infrastructure, Installing a cluster on OpenStack with Kuryr on your own infrastructure, Installing a cluster on OpenStack on your own SR-IOV infrastructure, Installing a cluster on OpenStack in a restricted network, Uninstalling a cluster on OpenStack from your own infrastructure, Installing a cluster on RHV with customizations, Installing a cluster on RHV with user-provisioned infrastructure, Installing a cluster on RHV in a restricted network, Installing a cluster on vSphere with customizations, Installing a cluster on vSphere with network customizations, Installing a cluster on vSphere with user-provisioned infrastructure, Installing a cluster on vSphere with user-provisioned infrastructure and network customizations, Installing a cluster on vSphere in a restricted network, Installing a cluster on vSphere in a restricted network with user-provisioned infrastructure, Uninstalling a cluster on vSphere that uses installer-provisioned infrastructure, Using the vSphere Problem Detector Operator, Installing a cluster on VMC with customizations, Installing a cluster on VMC with network customizations, Installing a cluster on VMC in a restricted network, Installing a cluster on VMC with user-provisioned infrastructure, Installing a cluster on VMC with user-provisioned infrastructure and network customizations, Installing a cluster on VMC in a restricted network with user-provisioned infrastructure, Understanding the OpenShift Update Service, Installing and configuring the OpenShift Update Service, Performing update using canary rollout strategy, Updating a cluster that includes RHEL compute machines, Showing data collected by remote health monitoring, Using Insights to identify issues with your cluster, Using remote health reporting in a restricted network, Troubleshooting CRI-O container runtime issues, Troubleshooting the Source-to-Image process, Troubleshooting Windows container workload issues, Extending the OpenShift CLI with plug-ins, Configuring custom Helm chart repositories, Knative CLI (kn) for use with OpenShift Serverless, Hardening Red Hat Enterprise Linux CoreOS, Replacing the default ingress certificate, Securing service traffic using service serving certificates, User-provided certificates for the API server, User-provided certificates for default ingress, Monitoring and cluster logging Operator component certificates, Retrieving Compliance Operator raw results, Performing advanced Compliance Operator tasks, Understanding the Custom Resource Definitions, Understanding the File Integrity Operator, Performing advanced File Integrity Operator tasks, Troubleshooting the File Integrity Operator, Allowing JavaScript-based access to the API server from additional hosts, Authentication and authorization overview, Understanding identity provider configuration, Configuring an HTPasswd identity provider, Configuring a basic authentication identity provider, Configuring a request header identity provider, Configuring a GitHub or GitHub Enterprise identity provider, Configuring an OpenID Connect identity provider, Using RBAC to define and apply permissions, Understanding and creating service accounts, Using a service account as an OAuth client, Understanding the Cluster Network Operator, Defining a default network policy for projects, Removing a pod from an additional network, About Single Root I/O Virtualization (SR-IOV) hardware networks, Configuring an SR-IOV Ethernet network attachment, Configuring an SR-IOV InfiniBand network attachment, About the OpenShift SDN default CNI network provider, Configuring an egress firewall for a project, Removing an egress firewall from a project, Considerations for the use of an egress router pod, Deploying an egress router pod in redirect mode, Deploying an egress router pod in HTTP proxy mode, Deploying an egress router pod in DNS proxy mode, Configuring an egress router pod destination list from a config map, About the OVN-Kubernetes network provider, Migrating from the OpenShift SDN cluster network provider, Rolling back to the OpenShift SDN cluster network provider, Configuring ingress cluster traffic using an Ingress Controller, Configuring ingress cluster traffic using a load balancer, Configuring ingress cluster traffic on AWS using a Network Load Balancer, Configuring ingress cluster traffic using a service external IP, Configuring ingress cluster traffic using a NodePort, Troubleshooting node network configuration, Associating secondary interfaces metrics to network attachments, Persistent storage using AWS Elastic Block Store, Persistent storage using GCE Persistent Disk, Persistent storage using Red Hat OpenShift Container Storage, AWS Elastic Block Store CSI Driver Operator, Red Hat Virtualization CSI Driver Operator, Image Registry Operator in OpenShift Container Platform, Configuring the registry for AWS user-provisioned infrastructure, Configuring the registry for GCP user-provisioned infrastructure, Configuring the registry for Azure user-provisioned infrastructure, Creating applications from installed Operators, Allowing non-cluster administrators to install Operators, Configuring built-in monitoring with Prometheus, Setting up additional trusted certificate authorities for builds, Creating CI/CD solutions for applications using OpenShift Pipelines, Working with OpenShift Pipelines using the Developer perspective, Reducing resource consumption of OpenShift Pipelines, Using pods in a privileged security context, Viewing pipeline logs using the OpenShift Logging Operator, Configuring an OpenShift cluster by deploying an application with cluster configurations, Deploying a Spring Boot application with Argo CD, Using the Cluster Samples Operator with an alternate registry, Using image streams with Kubernetes resources, Triggering updates on image stream changes, Creating applications using the Developer perspective, Viewing application composition using the Topology view, Working with Helm charts using the Developer perspective, Understanding Deployments and DeploymentConfigs, Monitoring project and application metrics using the Developer perspective, Adding compute machines to user-provisioned infrastructure clusters, Adding compute machines to AWS using CloudFormation templates, Automatically scaling pods with the horizontal pod autoscaler, Automatically adjust pod resource levels with the vertical pod autoscaler, Using Device Manager to make devices available to nodes, Including pod priority in pod scheduling decisions, Placing pods on specific nodes using node selectors, Configuring the default scheduler to control pod placement, Scheduling pods using a scheduler profile, Placing pods relative to other pods using pod affinity and anti-affinity rules, Controlling pod placement on nodes using node affinity rules, Controlling pod placement using node taints, Controlling pod placement using pod topology spread constraints, Running background tasks on nodes automatically with daemonsets, Viewing and listing the nodes in your cluster, Managing the maximum number of pods per node, Freeing node resources using garbage collection, Allocating specific CPUs for nodes in a cluster, Using Init Containers to perform tasks before a pod is deployed, Allowing containers to consume API objects, Using port forwarding to access applications in a container, Viewing system event information in a cluster, Configuring cluster memory to meet container memory and risk requirements, Configuring your cluster to place pods on overcommited nodes, Using remote worker node at the network edge, Red Hat OpenShift support for Windows Containers overview, Red Hat OpenShift support for Windows Containers release notes, Understanding Windows container workloads, Creating a Windows MachineSet object on AWS, Creating a Windows MachineSet object on Azure, Creating a Windows MachineSet object on vSphere, About the Cluster Logging custom resource, Configuring CPU and memory limits for Logging components, Using tolerations to control Logging pod placement, Moving the Logging resources with node selectors, Collecting logging data for Red Hat Support, Enabling monitoring for user-defined projects, Exposing custom application metrics for autoscaling, Recommended host practices for IBM Z & LinuxONE environments, Planning your environment according to object maximums, What huge pages do and how they are consumed by apps, Performance Addon Operator for low latency nodes, Optimizing data plane performance with the Intel vRAN Dedicated Accelerator ACC100, Overview of backup and restore operations, Installing and configuring OADP with Azure, Recovering from expired control plane certificates, About migrating from OpenShift Container Platform 3 to 4, Differences between OpenShift Container Platform 3 and 4, Installing MTC in a restricted network environment, Migration toolkit for containers overview, Editing kubelet log level verbosity and gathering logs, LocalResourceAccessReview [authorization.openshift.io/v1], LocalSubjectAccessReview [authorization.openshift.io/v1], ResourceAccessReview [authorization.openshift.io/v1], SelfSubjectRulesReview [authorization.openshift.io/v1], SubjectAccessReview [authorization.openshift.io/v1], SubjectRulesReview [authorization.openshift.io/v1], LocalSubjectAccessReview [authorization.k8s.io/v1], SelfSubjectAccessReview [authorization.k8s.io/v1], SelfSubjectRulesReview [authorization.k8s.io/v1], SubjectAccessReview [authorization.k8s.io/v1], ClusterAutoscaler [autoscaling.openshift.io/v1], MachineAutoscaler [autoscaling.openshift.io/v1beta1], HelmChartRepository [helm.openshift.io/v1beta1], ConsoleCLIDownload [console.openshift.io/v1], ConsoleExternalLogLink [console.openshift.io/v1], ConsoleNotification [console.openshift.io/v1], ConsoleQuickStart [console.openshift.io/v1], ConsoleYAMLSample [console.openshift.io/v1], CustomResourceDefinition [apiextensions.k8s.io/v1], MutatingWebhookConfiguration [admissionregistration.k8s.io/v1], ValidatingWebhookConfiguration [admissionregistration.k8s.io/v1], ImageStreamImport [image.openshift.io/v1], ImageStreamMapping [image.openshift.io/v1], ContainerRuntimeConfig [machineconfiguration.openshift.io/v1], ControllerConfig [machineconfiguration.openshift.io/v1], KubeletConfig [machineconfiguration.openshift.io/v1], MachineConfigPool [machineconfiguration.openshift.io/v1], MachineConfig [machineconfiguration.openshift.io/v1], MachineHealthCheck [machine.openshift.io/v1beta1], MachineSet [machine.openshift.io/v1beta1], AlertmanagerConfig [monitoring.coreos.com/v1alpha1], PrometheusRule [monitoring.coreos.com/v1], ServiceMonitor [monitoring.coreos.com/v1], EgressNetworkPolicy [network.openshift.io/v1], IPPool [whereabouts.cni.cncf.io/v1alpha1], NetworkAttachmentDefinition [k8s.cni.cncf.io/v1], PodNetworkConnectivityCheck [controlplane.operator.openshift.io/v1alpha1], OAuthAuthorizeToken [oauth.openshift.io/v1], OAuthClientAuthorization [oauth.openshift.io/v1], UserOAuthAccessToken [oauth.openshift.io/v1], Authentication [operator.openshift.io/v1], CloudCredential [operator.openshift.io/v1], ClusterCSIDriver [operator.openshift.io/v1], Config [imageregistry.operator.openshift.io/v1], Config [samples.operator.openshift.io/v1], CSISnapshotController [operator.openshift.io/v1], DNSRecord [ingress.operator.openshift.io/v1], ImageContentSourcePolicy [operator.openshift.io/v1alpha1], ImagePruner [imageregistry.operator.openshift.io/v1], IngressController [operator.openshift.io/v1], KubeControllerManager [operator.openshift.io/v1], KubeStorageVersionMigrator [operator.openshift.io/v1], OpenShiftAPIServer [operator.openshift.io/v1], OpenShiftControllerManager [operator.openshift.io/v1], OperatorPKI [network.operator.openshift.io/v1], CatalogSource [operators.coreos.com/v1alpha1], ClusterServiceVersion [operators.coreos.com/v1alpha1], InstallPlan [operators.coreos.com/v1alpha1], OperatorCondition [operators.coreos.com/v1], PackageManifest [packages.operators.coreos.com/v1], Subscription [operators.coreos.com/v1alpha1], ClusterRoleBinding [rbac.authorization.k8s.io/v1], ClusterRole [rbac.authorization.k8s.io/v1], RoleBinding [rbac.authorization.k8s.io/v1], ClusterRoleBinding [authorization.openshift.io/v1], ClusterRole [authorization.openshift.io/v1], RoleBindingRestriction [authorization.openshift.io/v1], RoleBinding [authorization.openshift.io/v1], AppliedClusterResourceQuota [quota.openshift.io/v1], ClusterResourceQuota [quota.openshift.io/v1], FlowSchema [flowcontrol.apiserver.k8s.io/v1alpha1], PriorityLevelConfiguration [flowcontrol.apiserver.k8s.io/v1alpha1], CertificateSigningRequest [certificates.k8s.io/v1], CredentialsRequest [cloudcredential.openshift.io/v1], PodSecurityPolicyReview [security.openshift.io/v1], PodSecurityPolicySelfSubjectReview [security.openshift.io/v1], PodSecurityPolicySubjectReview [security.openshift.io/v1], RangeAllocation [security.openshift.io/v1], SecurityContextConstraints [security.openshift.io/v1], StorageVersionMigration [migration.k8s.io/v1alpha1], VolumeSnapshot [snapshot.storage.k8s.io/v1], VolumeSnapshotClass [snapshot.storage.k8s.io/v1], VolumeSnapshotContent [snapshot.storage.k8s.io/v1], BrokerTemplateInstance [template.openshift.io/v1], TemplateInstance [template.openshift.io/v1], UserIdentityMapping [user.openshift.io/v1], Configuring the distributed tracing platform, Configuring distributed tracing data collection, Preparing your cluster for OpenShift Virtualization, Specifying nodes for OpenShift Virtualization components, Installing OpenShift Virtualization using the web console, Installing OpenShift Virtualization using the CLI, Uninstalling OpenShift Virtualization using the web console, Uninstalling OpenShift Virtualization using the CLI, Additional security privileges granted for kubevirt-controller and virt-launcher, Triggering virtual machine failover by resolving a failed node, Installing the QEMU guest agent on virtual machines, Viewing the QEMU guest agent information for virtual machines, Managing config maps, secrets, and service accounts in virtual machines, Installing VirtIO driver on an existing Windows virtual machine, Installing VirtIO driver on a new Windows virtual machine, Configuring PXE booting for virtual machines, Enabling dedicated resources for a virtual machine, Importing virtual machine images with data volumes, Importing virtual machine images into block storage with data volumes, Importing a Red Hat Virtualization virtual machine, Importing a VMware virtual machine or template, Enabling user permissions to clone data volumes across namespaces, Cloning a virtual machine disk into a new data volume, Cloning a virtual machine by using a data volume template, Cloning a virtual machine disk into a new block storage data volume, Configuring the virtual machine for the default pod network, Attaching a virtual machine to a Linux bridge network, Configuring IP addresses for virtual machines, Configuring an SR-IOV network device for virtual machines, Attaching a virtual machine to an SR-IOV network, Viewing the IP address of NICs on a virtual machine, Using a MAC address pool for virtual machines, Configuring local storage for virtual machines, Reserving PVC space for file system overhead, Configuring CDI to work with namespaces that have a compute resource quota, Uploading local disk images by using the web console, Uploading local disk images by using the virtctl tool, Uploading a local disk image to a block storage data volume, Managing offline virtual machine snapshots, Moving a local virtual machine disk to a different node, Expanding virtual storage by adding blank disk images, Cloning a data volume using smart-cloning, Using container disks with virtual machines, Re-using statically provisioned persistent volumes, Enabling dedicated resources for a virtual machine template, Migrating a virtual machine instance to another node, Monitoring live migration of a virtual machine instance, Cancelling the live migration of a virtual machine instance, Configuring virtual machine eviction strategy, Managing node labeling for obsolete CPU models, Diagnosing data volumes using events and conditions, Viewing information about virtual machine workloads, OpenShift cluster monitoring, logging, and Telemetry, Installing the OpenShift Serverless Operator, Listing event sources and event source types, Serverless components in the Administrator perspective, Integrating Service Mesh with OpenShift Serverless, Cluster logging with OpenShift Serverless, Configuring JSON Web Token authentication for Knative services, Configuring a custom domain for a Knative service, Setting up OpenShift Serverless Functions, Function project configuration in func.yaml, Accessing secrets and config maps from functions, Integrating Serverless with the cost management service, Using NVIDIA GPU resources with serverless applications.