Replies: 1 comment 4 replies
-
Please create a discussion for a particular case and link to a log bundle. This is a common case and most of the posted one are now solved.
The majority of these are baremetal installations, where install-config doesn't include most critical details (usually networking). So a "working install-config" won't be useful to anybody else.
We have automated tests which ensure each release works on most of the supported platforms (AWS, GCP and baremetal-via-assisted-installer). The only notable exceptions are Azure and arm64 (see related issues). |
Beta Was this translation helpful? Give feedback.
-
I have a general question and suggestion: why is it so quiet here? This google group okd-wg and github.com/okd-project/okd/discussions are the only communication channels on OKD. It is a very complex system with tens of installation flavors on tens of platforms. Releases are generated every few days with the latest updated often. On okd-wg I count 7 posts a month and on github some 10 discussions a month. I tried to look up the slack channel #openshift-users but it is reserved, on matrix.org chat we have just build notifications. I regularly build IPI vsphere clusters and since OKD 4.8 release I fail to stand up one. Posting failures is very difficult as there is so many moving parts. Would it make sense to start a registry of working install-config.yaml and description of the versions of the platforms used? At least at that point if someone says a particular release X is working on platform Y then it will tell us that we are doing something wrong.
Beta Was this translation helpful? Give feedback.
All reactions