docs, net, service-objects: Add a section for Service lifecycle by EdDev · Pull Request #969 · kubevirt/user-guide

EdDev · 2026-03-03T08:39:09Z

What this PR does / why we need it:

In v1.9 virtctl expose adds a ownerReference to the Service object and binds it to the VM/VMI object.
Allowing proper cleanup of Services and avoiding orphan services.

This change complements kubevirt/kubevirt#16884 by documenting it towards v1.9.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Design: A design document was considered and is present (link) or not required
PR: The PR description is expressive enough and will help future contributors
Code: Write code that humans can understand and Keep it simple
Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
Upgrade: Impact of this change on upgrade flows was considered and addressed if required
Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
Community: Announcement to kubevirt-dev was considered

Release note:

NONE

orelmisan

Thank you for the PR @EdDev!
Unfortunately, kubevirt/kubevirt#16884 didn't make it to the cut of release-1.8, so the feature will only be available in v1.9 (unless we backport of course).

aburdenthehand · 2026-03-12T14:47:35Z

/hold
I'd like to create a v1.8 branch after the release so that we have it ready for when we have versioning set up.

EdDev · 2026-03-19T07:50:38Z

Thank you for the PR @EdDev! Unfortunately, kubevirt/kubevirt#16884 didn't make it to the cut of release-1.8, so the feature will only be available in v1.9 (unless we backport of course).

Thank you. Done.

EdDev · 2026-03-19T07:51:54Z

/assign @orelmisan @frenzyfriday

orelmisan

Thank you for the change @EdDev.
Can you also adjust the version in the PR description?

orelmisan · 2026-03-22T10:06:13Z

+While creating the service explicitly, it is up to the user to explicitly
+cleanup the service.
+From v1.9 the implicit service creation through `virtctl expose` adds an
+`ownerRefernce` to the service object, binding the service to the VM/VMI.


Typo:

Suggested change

`ownerRefernce` to the service object, binding the service to the VM/VMI.

`ownerReference` to the service object, binding the service to the VM/VMI.

nit: Consider adding a link to https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/.

orelmisan · 2026-03-22T10:06:51Z

+
+## Service lifecycle
+
+Service objects may be created explicitly by an user or implicitly


Suggested change

Service objects may be created explicitly by an user or implicitly

Service objects may be created explicitly by a user or implicitly

orelmisan · 2026-03-22T10:08:11Z

+through the `virtctl expose` command.
+
+While creating the service explicitly, it is up to the user to explicitly
+cleanup the service.


nit:

Suggested change

cleanup the service.

clean up the service.

orelmisan · 2026-03-22T10:09:23Z

+`ownerRefernce` to the service object, binding the service to the VM/VMI.
+As a result, the service will be collected by the garbage-collector once


Suggested change

`ownerRefernce` to the service object, binding the service to the VM/VMI.

As a result, the service will be collected by the garbage-collector once

As a result, the service will be collected by the k8s garbage-collector once

EdDev · 2026-03-26T10:06:17Z

change: Rebase

In v1.9 `virtctl expose` adds a `ownerReference` to the Service object and binds it to the VM/VMI object. Allowing proper cleanup of Services and avoiding orphan services. Signed-off-by: Edward Haas <edwardh@redhat.com>

EdDev · 2026-03-26T10:14:27Z

change: Answered review comments from @orelmisan .

orelmisan

Thank you @EdDev!
/approve

kubevirt-bot · 2026-03-26T11:10:16Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: orelmisan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~docs/network/OWNERS~~ [orelmisan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

ormergi

LGTM

kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Mar 3, 2026

kubevirt-bot requested review from RamLavi and ormergi March 3, 2026 08:39

kubevirt-bot added the size/S label Mar 3, 2026

orelmisan reviewed Mar 10, 2026

View reviewed changes

kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 12, 2026

EdDev force-pushed the kubectl-expose-refown branch from 5325223 to 8cddf6f Compare March 19, 2026 07:50

kubevirt-bot assigned frenzyfriday and orelmisan Mar 19, 2026

orelmisan reviewed Mar 22, 2026

View reviewed changes

EdDev force-pushed the kubectl-expose-refown branch from 8cddf6f to 759f120 Compare March 26, 2026 10:06

docs, net, service-objects: Add a section for Service lifecycle

d4cf555

In v1.9 `virtctl expose` adds a `ownerReference` to the Service object and binds it to the VM/VMI object. Allowing proper cleanup of Services and avoiding orphan services. Signed-off-by: Edward Haas <edwardh@redhat.com>

EdDev force-pushed the kubectl-expose-refown branch from 759f120 to d4cf555 Compare March 26, 2026 10:13

orelmisan reviewed Mar 26, 2026

View reviewed changes

kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2026

ormergi approved these changes Mar 29, 2026

View reviewed changes

kubevirt-bot assigned ormergi Mar 29, 2026

kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2026

	`ownerRefernce` to the service object, binding the service to the VM/VMI.
	`ownerReference` to the service object, binding the service to the VM/VMI.


		## Service lifecycle

		Service objects may be created explicitly by an user or implicitly

		`ownerRefernce` to the service object, binding the service to the VM/VMI.
		As a result, the service will be collected by the garbage-collector once

Conversation

EdDev commented Mar 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

orelmisan left a comment

Choose a reason for hiding this comment

Uh oh!

aburdenthehand commented Mar 12, 2026

Uh oh!

EdDev commented Mar 19, 2026

Uh oh!

EdDev commented Mar 19, 2026

Uh oh!

orelmisan left a comment

Choose a reason for hiding this comment

Uh oh!

orelmisan Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

orelmisan Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

orelmisan Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

orelmisan Mar 22, 2026

Choose a reason for hiding this comment

Uh oh!

EdDev commented Mar 26, 2026

Uh oh!

EdDev commented Mar 26, 2026

Uh oh!

orelmisan left a comment

Choose a reason for hiding this comment

Uh oh!

kubevirt-bot commented Mar 26, 2026

Uh oh!

ormergi left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

EdDev commented Mar 3, 2026 •

edited

Loading