-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Adding to the test framework the equivalent to kubectl create -f. #9731
🌱 Adding to the test framework the equivalent to kubectl create -f. #9731
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test ? |
@adilGhaffarDev: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-cluster-api-e2e-full-release-1-4 |
2 similar comments
/test pull-cluster-api-e2e-full-release-1-4 |
/test pull-cluster-api-e2e-full-release-1-4 |
/pull-cluster-api-e2e-release-1-4 |
/test pull-cluster-api-e2e-full-release-1-4 |
/test pull-cluster-api-e2e-release-1-4 |
test/framework/cluster_proxy.go
Outdated
for _, o := range objs { | ||
if err := p.GetClient().Create(ctx, &o); err != nil { |
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.
for _, o := range objs { | |
if err := p.GetClient().Create(ctx, &o); err != nil { | |
for o := range objs { | |
if err := p.GetClient().Create(ctx, &objs[o]); err != nil { |
or reassign the iteration var
for _, o := range objs {
o := o
if err := p.GetClient().Create(ctx, &o); err != nil {
Signed-off-by: muhammad adil ghaffar <[email protected]>
054ae89
to
67b9656
Compare
/test pull-cluster-api-e2e-full-release-1-4 |
4/4 pull-cluster-api-e2e-full-release-1-4 passed (last passed: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/9731/pull-cluster-api-e2e-full-release-1-4/1725501937413001216) |
@adilGhaffarDev can you please remove WIP, if this is ready for review? Thanks! /test pull-cluster-api-e2e-full-release-1-4 |
5/6 passed, last failure was not at |
5/7 passed last failure was also related to ownerGraph issue which is in |
@@ -472,7 +472,7 @@ func createWorkloadClusterAndWait(ctx context.Context, input createWorkloadClust | |||
Expect(workloadClusterTemplate).ToNot(BeNil(), "Failed to get the cluster template") | |||
|
|||
Eventually(func() error { | |||
return input.Proxy.Apply(ctx, workloadClusterTemplate) | |||
return input.Proxy.Create(ctx, workloadClusterTemplate) | |||
}, 10*time.Second).Should(Succeed(), "Failed to apply the cluster template") |
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.
}, 10*time.Second).Should(Succeed(), "Failed to apply the cluster template") | |
}, 10*time.Second).Should(Succeed(), "Failed to create the cluster template") |
Q: what is the reason to use create instead of apply? |
As @killianmuldoon mentioned here #9696, it will help debug the flake we see in upgrade tests more specifically the one we are getting at Why did we add this to 1.4 instead of the main first? |
This is the same PR as https://github.com/kubernetes-sigs/cluster-api/pull/9736/files just for release-1.4, right? If yes, let's please hold this PR and continue with the other one. If we merged 9736 we should then cherry-pick back from there. To be clear, it's totally fine to have this PR to get data, but we should merge against main first and then backport instead of merging against release-1.4 first. |
And please add |
/hold |
/close because we merged #9737 which serves the same purpose. |
/close |
@sbueringer: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What this PR does / why we need it:
Adding runtime controller create for testing.
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 #