-
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]: restructure kubernetes integration tests #6260
[k8s]: restructure kubernetes integration tests #6260
Conversation
b9d00b0
to
684ef9a
Compare
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
Way cleaner, nice job!
I realised that if I merge this PR before this one I am gonna cause conflict to it. This is something I would like to avoid and I would rather update this one to include the former 🙂 |
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.
LGTM
684ef9a
to
8722836
Compare
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.
Nice!
|
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go Co-authored-by: Panos Koutsovasilis <panos.koutsovasilis@elastic.co>
* feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go Co-authored-by: Panos Koutsovasilis <panos.koutsovasilis@elastic.co>
#6268) * [k8s]: restructure kubernetes integration tests (#6260) * feat: restructure k8s integration tests * feat: update helm edot test (cherry picked from commit 79caf55) # Conflicts: # go.mod # testing/integration/otel_helm_test.go * fix: more conflicts * fix: go mod tidy * fix: update NOTICE.txt --------- Co-authored-by: Panos Koutsovasilis <panos.koutsovasilis@elastic.co>
What does this PR do?
This PR lays the groundwork for Kubernetes hints integration tests. The related commits of the former will be included in a follow-up PR (6fa8ffb, 9a48d02) as I want to keep this PR around 500 lines (excluding go.mod and NOTICE files). These changes address the need to avoid duplicating code logic, as hints tests require deploying plain Kubernetes YAML files and checking the agent status independently. Key updates include:
k8sContext
to standardize Kubernetes test setup.k8sCreateObjects
,k8sDeleteObjects
,k8sWaitForReady
) with better error handling.k8sCheckAgentStatus
.ReadyChecker
to validate readiness of Kubernetes objects (e.g., pods, deployments, daemonSets, statefulSets, etc.).These updates improve code readability, modularity, and reusability, reducing the need for duplicate logic in k8s tests.
Why is it important?
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 tool.Disruptive User Impact
No disruptive changes. Enhancements are internal to Kubernetes integration tests.
How to test this PR locally
Related issues