Bug 1648651

Summary:	The virtctl expose cmd is not consistent with kubectl expose
Product:	Container Native Virtualization (CNV)	Reporter:	Yan Du <yadu>
Component:	Networking	Assignee:	Sebastian Scheinkman <sscheink>
Status:	CLOSED ERRATA	QA Contact:	Yan Du <yadu>
Severity:	low	Docs Contact:
Priority:	medium
Version:	1.3	CC:	cnv-qe-bugs, danken, ncredi, sgordon
Target Milestone:	---
Target Release:	2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-24 20:15:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1644523

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 1 Yan Du 2018-11-19 06:35:04 UTC

https://github.com/kubevirt/kubevirt/pull/1716

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