Bug 1733523
| Summary: | [DOCS] No mention about adding Infrastructure node on bare metal UPI | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Daein Park <dapark> |
| Component: | Documentation | Assignee: | Cody Hoag <choag> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | sunzhaohua <zhsun> |
| Severity: | medium | Docs Contact: | Vikram Goyal <vigoyal> |
| Priority: | medium | ||
| Version: | 4.4 | CC: | aacostab, akiyoshi.yonekura, aos-bugs, choag, dsquirre, eponvell, gpei, hyoskim, jflynn, jhou, jlee, jokerman, kgarriso, mfuruta, oarribas, rbohne, rsandu, tkimura, toshio.oya, wsun, xtian |
| Target Milestone: | --- | Keywords: | CustomerScenariosInitiative, Reopened |
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-02 13:17:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
My customer met this issue in OCP4.3 and it will be same issue in OCP4.4 either, so I open again with changing the version as 4.4. This is not for 4.1 specific issue. This is about 4.x issue so we need this information with latest version My customer also met this issue in OCP4.4 We referred this way[1] which is mentioned in a mail-thread[2] to configure separated infra-node and I'm not sure this guidance[1] can be delivered to the customer officially. The customer wants official guidance to configure adding Infrastructure node on bare metal UPI. [1]https://github.com/lbohnsac/OCP4/tree/master/infrastructure-node-setup [2]http://post-office.corp.redhat.com/archives/openshift-sme/2020-May/msg00603.html I have attached another case for the same issue. This time the customer found and followed the KCS articles themselves, but they do not work as the cluster still only recognises the nodes as either master or worker. No infra nodes are found when checking OCM which meand the customer is still paying subscriptions on thesee nodes. Using infrastructure nodes is a supported feature to reduce subscription costs, but there is no official product documentation on how to implement this feature for UPI clusters. Please add documentation to support this feature. Hello Cody Hoag, Thank you so much for your time and efforts on product documents. As we seen it, we have done this already on the PR; https://github.com/openshift/openshift-docs/pull/24450 ,would we publish it on this BZ accordingly? Our partner NEC is waiting on this for a while and they would like to know the most current status. Would you please share it with us ? I am grateful for your help and clarification. Thank you, BR, Masaki @Jianwei would creating an infra node for bare metal UPI just follow the combination of these existing articles? 1. Create a worker machine following this [1]. 2. Add infra label to make it an infra node following this [2]. There are currently docs to complement the worker/infra node labeling discussion in progress, which can also be referred to when they're finished. [3] [1] https://docs.openshift.com/container-platform/4.6/machine_management/user_infra/adding-bare-metal-compute-user-infra.html [2] https://docs.openshift.com/container-platform/4.6/post_installation_configuration/cluster-tasks.html#creating-an-infra-node_post-install-cluster-tasks [3] https://github.com/openshift/openshift-docs/pull/28772 @Gaoyun Do you know the answers to my questions asked in comment#16? Or can you assign this to the appropriate person who could answer this? Thanks! (In reply to Cody Hoag from comment #16) > @Jianwei would creating an infra node for bare metal UPI just follow the > combination of these existing articles? > > 1. Create a worker machine following this [1]. > 2. Add infra label to make it an infra node following this [2]. > > There are currently docs to complement the worker/infra node labeling > discussion in progress, which can also be referred to when they're finished. > [3] > > [1] > https://docs.openshift.com/container-platform/4.6/machine_management/ > user_infra/adding-bare-metal-compute-user-infra.html > [2] > https://docs.openshift.com/container-platform/4.6/ > post_installation_configuration/cluster-tasks.html#creating-an-infra- > node_post-install-cluster-tasks > [3] https://github.com/openshift/openshift-docs/pull/28772 Yes, I think this works for bare metal UPI scenario. Closing as the changes have been merged into documentation with this PR - https://github.com/openshift/openshift-docs/pull/33057 Thanks! The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Document URL: * Creating infrastructure MachineSets [ https://docs.openshift.com/container-platform/4.1/machine_management/creating-infrastructure-machinesets.html ] Section Number and Name: N/A Describe the issue: This section describing about adding Infrastructure node, but the target environment is only AWS. v4.1 does not only support AWS IPI, but bare metal UPI, vSphere UPI, AWS UPI are also suppored. Suggestions for improvement: Add same section with IPI for AWS for bare metal UPI, at least, we should provide configuration steps and explanation about how to configure infrastructure node in UPI. It's important for CU's subscription counting. Additional information: User is usually considering to add infra node for logging, monitoring, ingress router components due to not counting as paid subscriptions.