OSDOCS-3887: add ELB switching feature

[jldohmann]

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-3887

Link to docs preview:

• updated assembly intro: http://file.rdu.redhat.com/jdohmann/OSDOCS-3887/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.html
• CLB -> NLB: http://file.rdu.redhat.com/jdohmann/OSDOCS-3887/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.html#nw-aws-switching-clb-with-nlb_configuring-ingress-cluster-traffic-aws
• NLB -> CLB: http://file.rdu.redhat.com/jdohmann/OSDOCS-3887/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.html#nw-aws-switching-nlb-with-clb_configuring-ingress-cluster-traffic-aws

Additional information:

[ocpdocs-previewbot]

🤖 Updated build preview is available at: https://50439--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/2404

[jldohmann]

@miheer could you PTAL for SME feedback? Thank you! 🙇

[candita]

/assign @Miciah @miheer

[jldohmann]

abc315e..8385ecb implement SME feedback pt. 1 8385ecb..4edd887 add sentence move note 4edd887..0a80706 add tip about when to use which method and fix typo 0a80706..10274b3 update admonitions and fix typo 10274b3..1247a6e implement SME feedback pt. 2 1247a6e..775be1aa fix typo 775be1aa..54d1cf82 implement peer review feedback pt.1 54d1cf82..f15d724 implement peer review feedback pt.2

[jldohmann]

@Miciah @miheer one question I have wrt the ingress outage that can occur: the use case between when a customer would use this new feature and when they would need to force replace the ingress controller is unclear to me. is this new feature meant to replace the old replacement procedure? or is there a difference that could impact whether a customer chooses one method over the other?

[Miciah]

@Miciah @miheer one question I have wrt the ingress outage that can occur: the use case between when a customer would use this new feature and when they would need to force replace the ingress controller is unclear to me. is this new feature meant to replace the old replacement procedure? or is there a difference that could impact whether a customer chooses one method over the other?

The new feature should result in a shorter duration of disruption (Miheer should have more precise numbers on how much disruption to expect). The old procedure is still useful if the cluster admin wants to change other parameters on the ingresscontroller, such as changing the domain, but in general, it makes sense to use the new procedure if the only goal is to change the LB type.

[jldohmann]

Thanks, I've pushed an update that adds a tip in the files to encourage users to use the method best suited for their goal. Please lmk what y'all think. In the meantime, I'd like to start the QE review process on this doc since it seems to be close to ready 🙂

@lihongan could you PTAL for QE ack? This is the documentation for the feature in NE-865. Thank you!

[lihongan]

@jldohmann it looks good to me. Thank you!

[jldohmann]

/cherrypick enterprise-4.12

[openshift-cherrypick-robot]

@jldohmann: new pull request created: #52117

In response to this:

/cherrypick enterprise-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.