Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add test coverage for adding/removing FD in KCP #11602

Open
fabriziopandini opened this issue Dec 20, 2024 · 1 comment
Open

Add test coverage for adding/removing FD in KCP #11602

fabriziopandini opened this issue Dec 20, 2024 · 1 comment
Labels
area/provider/control-plane-kubeadm Issues or PRs related to KCP area/testing Issues or PRs related to testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@fabriziopandini
Copy link
Member

fabriziopandini commented Dec 20, 2024 •
edited
Loading

While implementing #11598 I noticed that test coverage for failure domain management in KCP is minimal or not existent.

The PR partially addressed the tech debt by implementing test coverage for the failuredomains package (which was modified by the PR), but the upper layer of the call stack (scale.go, control_plane.go) still lack of test coverage, mostly with regards of scenarios where we are adding or removing failure domains.

/kind cleanup
/area provider/control-plane-kubeadm
@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. labels Dec 20, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 20, 2024
@fabriziopandini fabriziopandini added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/provider/control-plane-kubeadm Issues or PRs related to KCP and removed kind/bug Categorizes issue or PR as related to a bug. labels Dec 20, 2024
@fabriziopandini fabriziopandini mentioned this issue Dec 20, 2024
Merged
@sbueringer sbueringer added the area/testing Issues or PRs related to testing label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/provider/control-plane-kubeadm Issues or PRs related to KCP area/testing Issues or PRs related to testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbueringer @fabriziopandini @k8s-ci-robot