feat: show warnings on pod creation and two containers use the same port (#2240)

[lstocchi]

What does this PR do?

This PR proposes a way to guide users in case they try to create a pod with multiple containers and two or more of them use the same port

Screenshot/screencast of this PR

What issues does this PR fix or reference?

it resolves #2240

How to test this PR?

1. select two containers using the same port
2. create a pod from them
3. in the create pod page you should see the warning

[deboer-tim]

+1 on the function. I don't love banner warning UI and it doesn't match anything else (because we don't have a similar issue anywhere else yet), but we could always get design input and change it later.

[mairin]

I see where you got the design idea for the Possible Runtime Error alert message... it looks like the Patternfly alert, but it's too bright I think for our theme. I created one of these for the OpenShift Local mockup, looks like this:

I think a similar look could work a little better here. (I will mock smtg up, will post later today)

[mairin]

What do you think about this? Here's the details:

• fill: charcoal-600
• yellow highlight color + header text color: amber-400
• yellow icon color: amber-500
• icon: font awesome triangle-exclamation
• font size: 14pt

[lstocchi]

I see where you got the design idea for the Possible Runtime Error alert message... it looks like the Patternfly alert

I copied the alert notification from the tailwindcss page https://v1.tailwindcss.com/components/alerts#left-accent-border

What do you think about this? Here's the details:

Much much better, thanks!! I'll update the PR to this 🙏

[jeffmaury]

If there are several ports in conflicts, the message is:

Can we switch to:

Containers a and b use the same ports c and d ?

[lstocchi]

Containers a and b use the same ports c and d ?

Done. You can see the result in the gif https://user-images.githubusercontent.com/49404737/242282201-241ee8e5-129f-413d-9009-9e1dcfcf78a8.gif

[mairin]

That looks fantastic @lstocchi!!!

[jeffmaury]

I had 2 containers:

• one was using ports 8080 and 5000
• second one using 8080 and 8443

First was stopped and second running.

Here's what I got:

[lstocchi]

Ops my bad, i only focussed to see the results with multiple ports and i didn't check in other cases. Added another test for that. Please try again.

[jeffmaury]

LGTM

[cdrage]

Thanks @lstocchi was able to test this out and it warned correctly when using the same port against a wordpress + another wordpress container + mysql setup.

Code looks good too.

LGTM!