Skip to content

modify ServiceType LoadBalancer -> NodePort, service Port's nodePort as the host cluster may have already allocated this port number #3171

@Lanyujiex

Description

@Lanyujiex

There is a certain probability of service nodeport duplication, as the host cluster may have already allocated this port number. This can lead to successful modifications within the vcluster, but the changes cannot be synchronized to the host cluster.

my error logs:

2025-09-04 14:44:03     ERROR   controller/controller.go:341    Reconciler error        {"component": "vcluster", "controller": "service", "namespace": "default", "name": "deepseek-svc", "reconcileID": "a4b4b229-3bd4-4784-9ba3-650c71f734b5", "error": "sync: patch host object: update object: Service \"deepseek-svc-x-default-x-tenant-61616664-textxl\" is invalid: spec.ports[0].nodePort: Invalid value: 30080: provided port is already allocated"}

Do we have any good solutions to this problem?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions