Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-9009

Provide details about the impact of installing "workers" with replica 1 in the infrastructureTopology

XMLWordPrintable

    • Moderate
    • 3
    • OSDOCS Sprint 234, OSDOCS Sprint 235
    • 2
    • Unspecified
    • If docs needed, set a value

      Document URL:

      https://docs.openshift.com/container-platform/4.8/installing/installing_bare_metal/installing-bare-metal-network-customizations.html#installation-bare-metal-config-yaml_installing-bare-metal-network-customizations

      Section Number and Name:

      At the 'Sample install-config.yaml file for bare metal'
      Point 4

      Describe the issue:

      When setting worker 1, the infrastructureTopology understands as "SingleReplica" which causes infra components to only have 1 replica, such as prometheus.

      Currently, this effect is not described in any part of the documentation, causing confusion when issues arrises like pods not having HA replicas as would be expected per default.

      Suggestions for improvement:

      Provide details as described at:
      https://github.com/openshift/enhancements/blob/ce4d303db807622687159eb9d3248285a003fabb/enhancements/single-node/cluster-high-availability-mode-api.md?plain=1#L113-L117

      ~~~
      When worker replica count is `0`, the control plane nodes are also configured as workers. Therefore the `infrastructureTopology`
      value will be the same as the `controlPlaneTopology` value. When the worker replica count is `1`, the `infrastructureTopology` is set to `SingleReplica`. Otherwise it is set to `HighlyAvailable`.
      ~~~

      Additional information:

            sdudhgao@redhat.com Servesha Dudhgaonkar
            rhn-support-hgomes Hevellyn Gomes
            Red Hat Employee
            Hevellyn Gomes
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: