Based on slack: https://redhat-internal.slack.com/archives/C0534HDGBNW/p1693395993366979

To be done for 4.13 clusters:

• On the Day 1, add an info alert mentioning that custom managed ingress values might not work and render external link to the article 7028653
• On the Day 2, keep the button "Edit application ingress" always disabled, the tooltip will state a brief reason.
• On the Day 2, the fields on the Application ingress card will stay visible&read-only as they recently are (so no change)
• On the Day 2, show inline info alert with a brief explanation and providing a link to the article

Based on https://redhat-internal.slack.com/archives/C0534HDGBNW/p1693481819997809 and https://redhat-internal.slack.com/archives/C0534HDGBNW/p1693481964954729:

To be done for 4.13 clusters:

• Hide the fields in Day 1
• On the Day 2, keep the fields editable as they recently are, the Save might fail with the backend error referencing article with description of a workaround

Keep the functionality as it is for OCP 4.14 and newer.

Keep the fields hidden as they recently are for OCP 4.12 or older.

Future work (out of scope here):

• the backend will provide indicator whether particular 4.13 cluster has the feature supported. Once we have that, the UI can disable/enable the edit functionality in Day 2.