-
Notifications
You must be signed in to change notification settings - Fork 260
[CI] Add Cyclonus to merge validation #860
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
Conversation
dd53e3c to
8b8788d
Compare
test/cyclonus/install-cyclonus.yaml
Outdated
| name: cyclonus | ||
| imagePullPolicy: IfNotPresent | ||
| image: mfenwick100/cyclonus:v0.4.4 | ||
|
|
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.
reason for newline here?
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.
It seems it will be nice to have flexibility to control command later to have various testing environment.
| kubectl apply -f ./npm/azure-npm.yaml | ||
| - name: Run Cyclonus network policy test | ||
| run: make test-cyclonus |
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.
NPM has dependency about telemetricHandle before running each controller. Does it have enough time to fail them to start each controller before running test-cyclonus when using kind cluster? If not, it may fail some of the first testsets. Can you check it in log files? We eventually remove these dependency later.
638d6b4 to
0b68bac
Compare
c5c353d to
f29ca15
Compare
JungukCho
left a comment
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!
Reason for Change:
Issue Fixed:
Requirements:
Notes: