Bug 1648651 - The virtctl expose cmd is not consistent with kubectl expose
Summary: The virtctl expose cmd is not consistent with kubectl expose
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 1.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 2.0
Assignee: Sebastian Scheinkman
QA Contact: Yan Du
URL:
Whiteboard:
Depends On:
Blocks: 1644523
TreeView+ depends on / blocked
 
Reported: 2018-11-11 12:00 UTC by Yan Du
Modified: 2019-07-24 20:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-24 20:15:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:1850 0 None None None 2019-07-24 20:15:59 UTC

Description Yan Du 2018-11-11 12:00:55 UTC
Description of problem:

The virtctl expose cmd is not consistent with kubectl expose

For kubectl expose, there is no --node-port parameter
For virtctl expose, there is a --node-port parameter

https://bugzilla.redhat.com/show_bug.cgi?id=1644523#c6

Version-Release number of selected component (if applicable):
openshift v3.11.16
kubernetes v1.11.0+d4cacc0
CNV1.3

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
The virtctl expose cmd is not consistent with kubectl expose

Expected results:
--node-port parameter should be removed.

Additional info:

Comment 2 Yan Du 2019-03-27 02:31:44 UTC
Test on d/s build 1.4 and u/s build v0.15.0, --node-port flag have been removed.
$ virtctl expose vmi vmi-fedora --port=22 --target-port=22 --type=NodePort --node-port=30001 --name=testport
unknown flag: --node-port

Comment 4 errata-xmlrpc 2019-07-24 20:15:50 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/RHEA-2019:1850


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