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 cases for RKE2 Controller #235

Open
salasberryfin opened this issue Jan 12, 2024 · 2 comments
Open

Add test cases for RKE2 Controller #235

salasberryfin opened this issue Jan 12, 2024 · 2 comments
Labels
area/testing Indicates an issue related to test kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. status/help wanted Extra attention is needed triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@salasberryfin
Copy link
Contributor

salasberryfin commented Jan 12, 2024 •
edited
Loading

Describe the solution you'd like:
As a developer, I want to be able to validate the functionality of the rke2config_controller, to have confidence that the reconcile loop is behaving as expected.

Why do you want this feature:
To easily identify errors in the RKE2 Config reconcile loop.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
@salasberryfin salasberryfin added kind/feature New feature or request needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. area/testing Indicates an issue related to test labels Jan 12, 2024
@salasberryfin salasberryfin mentioned this issue Jan 12, 2024
Merged
4 tasks
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 12, 2024
@alexander-demicev alexander-demicev added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 27, 2024
@furkatgofurov7 furkatgofurov7 added the status/help wanted Extra attention is needed label Aug 28, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 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/testing Indicates an issue related to test kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. status/help wanted Extra attention is needed triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@salasberryfin @alexander-demicev @furkatgofurov7