search

kubevirt / user-guide

This user guide will walk you through installation and various features.
https://kubevirt.io/user-guide
Apache License 2.0
64 stars 234 forks source link

unknown flag: --node-port #807

Closed jokuniew closed 2 weeks ago

jokuniew commented 5 months ago

Description: When I use the command from the doc Expose VirtualMachineInstance as a NodePort Service $ virtctl expose virtualmachineinstance vmi-ephemeral --name nodeport --type NodePort --port 27017 --target-port 22 --node-port 30000 It gives following error: unknown flag: --node-port

I assume, that --node-port flag was removed after this disscussion https://bugzilla.redhat.com/show_bug.cgi?id=1644523 in this PR https://github.com/kubevirt/kubevirt/pull/1716 But doc wasn't updated since then

What you expected: Working command for exposing vms ssh access through nodeport

URL: Expose VirtualMachineInstance as a NodePort Service

Additional context: none

kubevirt-bot commented 2 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 1 month ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 2 weeks ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 2 weeks ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/user-guide/issues/807#issuecomment-2466781926): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.