-
Notifications
You must be signed in to change notification settings - Fork 154
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.
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
[k8s]: transition integration tests to adapter pattern #6277
[k8s]: transition integration tests to adapter pattern #6277
Conversation
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
@blakerouse @swiatekm could you give this PR a review? 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me overall, left some comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, test are more readable by refactoring common boilerplate in separate functions.
* feat: transition kubernetes integration tests to adapter pattern * fix: count nodes without NoSchedule taints (cherry picked from commit 67c744f)
* feat: transition kubernetes integration tests to adapter pattern * fix: count nodes without NoSchedule taints (cherry picked from commit 67c744f)
* feat: transition kubernetes integration tests to adapter pattern * fix: count nodes without NoSchedule taints (cherry picked from commit 67c744f)
What does this PR do?
This PR continues the groundwork for Kubernetes hints integration tests. The next and last episode of this PR-series can be seen here 2ea1f2f. Again these were split up because I want to keep each PR around 500 lines.
Key changes in this PR:
Transition Kubernetes integration tests to an "adapter" pattern:
k8sTestStep
functions that encapsulate individual test steps for clarity and flexibility.k8sStepCreateNamespace
,k8sStepDeployKustomize
, andk8sStepRunInnerTests
.Align all kubernetes integration tests:
skipReason
.Why is it important?
The adapter pattern for Kubernetes integration tests enhances readability, maintainability, making it easier to add or modify test cases.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding changes to the default configuration files[ ] I have added an entry in./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues