Single master aws install

[sst1xx]

Describe the bug
Hi everybody,
probably that single master install instruction doesn't seem to be correct

Version

IPI openshift-install 4.6.0-0.okd-2020-12-12-135354
AWS

How reproducible

The issue is reproducible - 100%
Generate install-config.yaml
Use the following settings:

compute:
- name: worker
  replicas: 0
controlPlane:
  name: master
  replicas: 1

Log bundle

DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: downloading update 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 6% complete 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 7% complete 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 78% complete 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 84% complete 
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 89% complete 
DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1 
ERROR Cluster operator authentication Degraded is True with WellKnownReadyController_SyncError: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1 
INFO Cluster operator authentication Available is False with WellKnown_NotReady: WellKnownAvailable: The well-known endpoint is not yet available: need at least 3 kube-apiservers, got 1 
INFO Cluster operator insights Disabled is True with Disabled: Health reporting is disabled 
FATAL failed to initialize the cluster: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1 

[vrutkovs]

Seems single master mode in installer needs a few more changes.

Try applying this:

apiVersion: operator.openshift.io/v1
kind: Authentication
metadata:
  name: cluster
spec:
  unsupportedConfigOverrides:
    useUnsupportedUnsafeNonHANonProductionUnstableOAuthServer: true

[sst1xx]

@vrutkovs thank you Vadim for such prompt response!
But sorry for silly question.
Would you mind showing me how to apply this settings before cluster installation please?

[vrutkovs]

See https://github.com/openshift/installer/blob/master/docs/user/customization.md#kubernetes-customization-unvalidated.

If it fixes the issue and necessary to stand up a cluster we can patch it in OKD 4.6 installer

[sst1xx]

omg, I did not see this. Thank you once more time. I'm going to check it and provide the result.

[sst1xx]

Probably I did something wrong, but I am still receiving this error

INFO Waiting up to 40m0s for the cluster at https://api.domain.com:6443 to initialize...
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2020-12-12-135354: 79% complete
DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1

tree

.
├── manifests
│   ├── 04-openshift-machine-config-operator.yaml
│   ├── cluster-config.yaml
│   ├── cluster-dns-02-config.yml
│   ├── cluster-infrastructure-02-config.yml
│   ├── cluster-ingress-02-config.yml
│   ├── cluster-network-01-crd.yml
│   ├── cluster-network-02-config.yml
│   ├── cluster-proxy-01-config.yaml
│   ├── cluster-scheduler-02-config.yml
│   ├── cvo-overrides.yaml
│   ├── etcd-ca-bundle-configmap.yaml
│   ├── etcd-client-secret.yaml
│   ├── etcd-metric-client-secret.yaml
│   ├── etcd-metric-serving-ca-configmap.yaml
│   ├── etcd-metric-signer-secret.yaml
│   ├── etcd-namespace.yaml
│   ├── etcd-service.yaml
│   ├── etcd-serving-ca-configmap.yaml
│   ├── etcd-signer-secret.yaml
│   ├── kube-cloud-config.yaml
│   ├── kube-system-configmap-root-ca.yaml
│   ├── machine-config-server-tls-secret.yaml
│   └── openshift-config-secret-pull-secret.yaml
└── openshift
    ├── 99_cloud-creds-secret.yaml
    ├── 99_kubeadmin-password-secret.yaml
    ├── 99_openshift-cluster-api_master-machines-0.yaml
    ├── 99_openshift-cluster-api_master-user-data-secret.yaml
    ├── 99_openshift-cluster-api_worker-machineset-0.yaml
    ├── 99_openshift-cluster-api_worker-user-data-secret.yaml
    ├── 99_openshift-machineconfig_99-master-ssh.yaml
    ├── 99_openshift-machineconfig_99-worker-ssh.yaml
    ├── 99_openshift-single-master-etcd.yaml
    ├── 99_openshift-single-master-ingress.yaml
    ├── 99_role-cloud-creds-secret-reader.yaml
    ├── openshift-install-manifests.yaml
    └── single-master.yaml

cat ./openshift/single-master.yaml

apiVersion: operator.openshift.io/v1
kind: Authentication
metadata:
  name: cluster
spec:
  unsupportedConfigOverrides:
    useUnsupportedUnsafeNonHANonProductionUnstableOAuthServer: true

[vrutkovs]

This should be auto-added by installer since 4.6.0-0.okd-2021-01-15-162431.

Please give the latest 4.6 nightly a try and link to must-gather if its still doesn't come up out of the box

[sst1xx]

Despite the fact that the setup process could not be finished and some error messages I was able to login into cluster.
Thank you @vrutkovs so much!

* Cluster operator monitoring is reporting a failure: Failed to rollout the stack. Error: running task Updating Prometheus-k8s failed: reconciling Prometheus rules PrometheusRule failed: updating PrometheusRule object failed: Internal error occurred: failed calling webhook "prometheusrules.openshift.io": Post "https://prometheus-operator.openshift-monitoring.svc:8080/admission-prometheusrules/validate?timeout=5s": x509: certificate signed by unknown authority
DEBUG Still waiting for the cluster to initialize: Working towards 4.6.0-0.okd-2021-01-15-162431: 89% complete
DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1
DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1
DEBUG Still waiting for the cluster to initialize: Cluster operator authentication is reporting a failure: WellKnownReadyControllerDegraded: need at least 3 kube-apiservers, got 1