-
Notifications
You must be signed in to change notification settings - Fork 431
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
Refactor infrastructure-azure templates required by CAPI tests to match CAPD #1423
Refactor infrastructure-azure templates required by CAPI tests to match CAPD #1423
Conversation
/test pull-cluster-api-provider-azure-capi-e2e |
6440913
to
0f73357
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
0f73357
to
bd4927b
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
bd4927b
to
5d9dc2b
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
1 similar comment
/test pull-cluster-api-provider-azure-capi-e2e |
/retest |
40288fa
to
41045ca
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
41045ca
to
b7ed98a
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
1 similar comment
/test pull-cluster-api-provider-azure-capi-e2e |
/retest |
1 similar comment
/retest |
/test pull-cluster-api-provider-azure-capi-e2e |
2 questions;
|
removed, it was pushed by mistake
for now I added them to .gitignore (same as CAPI docker e2e templates). No strong opinion here but I was thinking it doesn't really make sense to check them in since they are only used by e2e and get generated when e2e runs. |
cea9f92
to
b1c570e
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
b1c570e
to
8ce43df
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
8ce43df
to
de1bf7b
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
1 similar comment
/test pull-cluster-api-provider-azure-capi-e2e |
kubernetes-sigs/cluster-api#4830 should help with the drain timeout test (VM deletion is timing out), will disable it until we can pull it in |
3f1217b
to
e834444
Compare
/test pull-cluster-api-provider-azure-capi-e2e |
/retest |
@nader-ziada this is ready besides the fact that I'm running into the same flake as described in #1440 /retest |
/lgtm will check back in a bit on the e2e run |
the last run passed, will monitor the health of the periodic job /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-provider-azure-e2e |
What type of PR is this?
What this PR does / why we need it: Instead of having static templates for capi e2e tests with lots of duplicated yaml, use kustomize to generate the required templates for the CAPI e2e suite. The templates were added to gitignore so they are not checked into code.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: