The health check editor shouldn't block users from picking ports that aren't in the pod spec since other ports can be exposed. This is particularly true when editing an existing probe since an existing value might get cleared. $ oc explain pods.spec.containers.ports KIND: Pod VERSION: v1 RESOURCE: ports <[]Object> DESCRIPTION: List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed. Any port which is listening on the default "0.0.0.0" address inside a container will be accessible from the network. Cannot be updated. ContainerPort represents a network port in a single container.
Created attachment 1689750 [details] port is required field
I have validated the bugzilla on the Build: 4.5.0-0.ci-2020-05-18-204038 Browser: Google Chrome Version 81.0.4044.129 Please have a look at the shared screenshot Marking this as verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409