Bug 1826050 - Health check editor shouldn't restrict HTTP ports to those in pod spec
Summary: Health check editor shouldn't restrict HTTP ports to those in pod spec
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Vikram Raj
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-20 18:54 UTC by Samuel Padgett
Modified: 2020-07-13 17:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Version: 4.5.0-0.ci-2020-04-17-015018 Cluster ID: a4344ab4-2501-4fee-90e4-5242c008eacf Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0
Last Closed: 2020-07-13 17:29:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
port is required field (116.99 KB, image/png)
2020-05-19 06:08 UTC, Gajanan More
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5401 0 None closed Bug 1826050: Health check editor shouldn't restrict ports to those in pod spec 2020-06-23 10:08:41 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:29:31 UTC

Description Samuel Padgett 2020-04-20 18:54:37 UTC
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.

Comment 4 Gajanan More 2020-05-19 06:08:12 UTC
Created attachment 1689750 [details]
port is required field

Comment 5 Gajanan More 2020-05-19 06:08:46 UTC
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

Comment 6 errata-xmlrpc 2020-07-13 17:29:11 UTC
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


Note You need to log in before you can comment on or make changes to this bug.