-
Notifications
You must be signed in to change notification settings - Fork 93
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
Add target status integration tests #604
Conversation
e3d07c4
to
e44f0b8
Compare
e44f0b8
to
f58d7f8
Compare
cc @bwplotka |
6dafdeb
to
9d1c5e8
Compare
6582a07
to
907e15e
Compare
907e15e
to
d4fc417
Compare
d4fc417
to
0b2a919
Compare
// To make tests simple and fast, the test suite runs the operator internally. The CRDs | ||
// are expected to be installed out of band (along with the operator deployment itself in | ||
// a real world setup). | ||
package e2e |
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.
wowow - this is quite next level and quite innovating. Probably good for fun blog post / separate OSS lib / contribution to k8s testing libs or so 🙈
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 solid, thanks for this work! 💪🏽 A bit a lot of low level code to maintain, but well readable & for good reasons, thanks!
Slightly different approach from #395. The problem is that when we run an operator within the test, the HTTP client cannot resolve Pod IP addresses. The resolve this, I created a custom HTTP client which can do this.
This PR builds on top of #613 since we now check if collectors are ready before checking whether target status is working.