Skip to content

kubeconfig endpoint not updated when TCP ingress hostname is modified #747

@joseluisgonzalezca

Description

@joseluisgonzalezca

Context

I have a working ControlPlane deployed with Kamaji. The controlplane endpoint is provided with an Ingress resource. If that Ingress hostname is modified, all related resources are updated accordingly except from the kubeconfig server field. This issue can be in some way related to #734 .

Kamaji Version

The bug can be reproduced with edge-25.3.2 version.

Current behaviour

Kamaji reconciler process in not modifying all required resources when the ingress hostname changes. The Ingress resource is updated with all the related certificates. However, kubeconfig server parameter is not updated.

Expected behaviour

admin-kubeconfig must be updated/recreated when the Ingress resource is modified.

Thanks!

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