okd.io | Source files used to build the https : //www.okd.io site

I have been working on an installation of OKD on an air-gapped environment. The first major step has been mirroring the OKD images so that they can be moved over to the new environment and pulled locally. I've been following a combination of the OpenShift documentation and this article, as well as this resource for getting my certificates set up. I have been making slow but consistent progress.

However, I am now having trouble when attempting to actually mirror the files using

I recently deployed a version 4.5 OKD cluster and everything seems fine, but I can't get the Google identity provider to work for signing in. I followed the instructions here, but with no success. When I try to log in with my company google identity I get a very generic error message:

login error

I ended up with the following OAuth config:

Openshift/okd version: 3.11

I'm using jenkins-ephemeral app from the openshift catalog and using a buildconfig to create a pipeline. Reference: https://docs.okd.io/3.11/dev_guide/dev_tutorials/openshift_pipeline.html

When i start the pipeline, in one the stage of jenkins it needs to create a persistent volume, at that point im getting the following error:

Since Docker can now run on Windows, is there a way to deploy Openshift OKD over a Windows VM?

In the documentation under System and environment requirements we can read that rhel family OS are needed, but I'm just wondering if there is a side process (alternative) process to perform this operation.

My main concern is that I need to run Windows containers on OKD.

I need to update a file using ansible. In manual process of updating, when the edit command is ran, the file opens in a editor like vim, nano etc, where the changes are updated and saved.

i.e, Upon running of following command, a temp-file gets opened in editor specified in the command, sudo OC_EDITOR="nano" oc edit configmap/webconsole-config -n openshift-web-console

Note that each time when the command is ran the content gets opened in new temp files. Once the changes are updated the file gets saved into the docker container.

Since in the above command the editor is specified as nano, the file contents are opened in nano editor with content as follows:

Can OpenShift Origin (OKD) be installed on RHEL 8? The documentation states minimal RHEL 7.4 or later: https://docs.okd.io/latest/install/prerequisites.html

However, RHEL 8 seems to be a major rework going on par with the commercial OpenShift 4. So I would assume the best version of RHEL to install OKD on is RHEL 7.6. Am I correct?

I have an OKD cluster setup with EFK stack for logging, as described here. I have never worked with one of the components before.

One deployment logs requests that contain a specific value that I'm interested in. I would like to extract just this value and visualize it with an area map in Kibana that shows the amount of requests and where they come from.

The content of the message field basically looks like this:

There are several ways to make a build for Openshift, one of them is Docker build strategy

I do have a Dockerfile in the root of my repository:

When I installed our cluster, I used a self signed cert from our internal CA authority. Everything was fine until I started getting cert errors from applications that I was deploying to the OKD cluster. We decided instead of trying to fix the errors one at a time for all time, we would simply purchase a commercial cert and install that. So we bought a SAN cert, with wildcards (identical to the one we got from our internal CA originally) from GlobalSign and I'm trying to install it with huge problems.

Keep in mind, I have tried dozens of iterations here. I'm just documenting the last one I have tried in an attempt to figure out what the hell is the problem. This is on my test cluster, which is a VM server and I revert to a snapshot after every one. The snapshot is the operational cluster using the internal CA certs.

So, my first step was to build my CAfile to be passed in. I downloaded the root and intermediate certs for GlobalSign and put them in the ca-globalsign.crt file. (PEM formatted)

when i run