I've deployed successfully. The only thing I would ask for is a dependency on the openshift-ansible package for Ansible 2.6.x. The release notes already say it needs to be 2.6+, but the install fails with 2.7.x.

I'd like to ask anyone who deployed OKD 3.11 successfuly if you could reply to this thread with your ack or nack. We need this feedback in order to promote to -candidate and then the official CentOS repos.

First of all sorry for the late reply as well as
for any confusion i may have caused with my previous
email.

I was very pleased to see the vibe and excitement
around testing OKD v3.11, very much appreciated.

Here are the latest info:

everyone who wants to help us with testing
should use [1] repo which can be consumed:

in the inventory as [2] or

by deploying your own repo file [3]

nobody should use the repo i've mentioned in
my previous email [4] (CentOS Infra team
corrected me on the confusion i made, once again
apologies for that)

Regarding the ansible version here are the info
following my sync up with CentOS Infra team:

very likely on Monday/ latest Tuesday a new
rpm called centos-release-ansible26 will appear
in CentOs Extras

the above rpm will become a dependency for the
centos-release-openshift-origin311 rpm
which will be created and land in CentOS Extras
repo at the same time OKD v3.11 will be promoted
to mirror.centos.org

note this is the same flow as it was for all
versions prior to v3.11 ( the rpm provides the
CentOS repo location for OKD rpms).

Note:

if your flow up until now was to never use centos-release-openshift-originXXX
rpm and you were creating your own repo files
then you will need to make sure you pull as
dependency the ansible 2.6.x (together with
its own dependencies) rpm. It is up to you
from where you are going to pull the ansible
rpm: from Epel, from CentOS Extras etc.

with the above we are trying to have a
single way of solving the ansible dependency
problem

We would like to announce that OKD v3.11 rpms
are available for testing at [1].

As such we are calling for help from community to
start testing and let us know if there are issues with
the rpms
and its dependencies.

And in the spirit of transparency see below the
plan to promote the rpms
to mirror.centos.org
repo:

in the next few days the packages should be
promoted to the test repo
[2] (currently it does not exist, we are waiting
to be sync'ed
in the background)

in one/two weeks time if we haven't heard any
issues/ blockers we are going to promote to [3] repo
(currently it doesn't exist, it will once the rpm
will be promoted and signed)

Please note the ansbile
version use (and supported) must be
2.6.x and not 2.7, if you opt to ignore the warning
you will run into issues.

On a different note the CentOS
Infra team are working hard (thanks !) to package
and release a centos-ansible
rpm which we'll promote in our PaaSrepos.

The rational is to bring more control around the
ansible
version used/ required by OpenShift-ansible
installer and not rely on the latest ansbile
version pushed to epelrepo
we caused friction recently (reflected on our CI as
well as users reporting issues)