-
Notifications
You must be signed in to change notification settings - Fork 209
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
Drop cilium endpoint verification. #2205
Conversation
…t's disabled. Signed-off-by: viktor-kurchenko <viktor.kurchenko@isovalent.com>
e7b166a
to
16344bf
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.
Looks great, thanks for the updates
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.
I have a concern below about the behaviour of the testsuite with this proposal.
No need to block on my feedback. We can discuss a little more but I'm fine with the solution in principle.
Signed-off-by: viktor-kurchenko <viktor.kurchenko@isovalent.com>
I think it would be useful to include the context in the description that: This is no longer needed because Cilium should be already provisioned correctly in the environment before deploying the connectivity apps, and these tests already validate that the k8s deployment resource is ready before continuing. |
Looks like Cilium endpoint verification is no longer needed because Cilium should be already provisioned correctly in the environment before deploying the connectivity apps, and these tests already validate that the k8s deployment resource is ready before continuing.
This should also unblock connectivity tests for Customers that have
disableEndpointCRD: "true"
property configured.