PR Blocking test(s)

[detiber]

/kind feature

create and wire up pr-blocking integration tests

/assign @liztio

[liztio]

what sort of things qualify as "integration tests" here? What's our test for completion?

[detiber]

@liztio ideally we'd do a live test where we actually exercise the creation of a cluster using cluster-api and perform a minimal smoke test that the cluster appears to be functional. I do not think that this needs to include the full clusterctl workflow, since that introduces additional cleanup/teardown issues and also drastically increases the test time.

[liztio]

/lifecycle active

[detiber]

/priority critical-urgent

[liztio]

/lifecycle active

[timothysc]

In an ideal world we would test the following on a per PR basis:

• [MVP] Behavioral Tests
  • Infrastructure (vpc, etc) has been stood up according to the declarative spec
    • Traffic inside of the vpc are routable
    • Check the health of etcd
    • At a minimum, we need verification of (quick-test)

---

As a follow on we will open an issue to enumerate the future test blocking issues.

• [Future] Integration Tests
  • Standup, and Teardown
  • (TODO) Define the breakout here.
• [Future] All behavioral level conformance tests are run (sonobuoy)
• [Future] Traffic has been verified to (ingress is accessible)

[liztio]

update on this: we're blocked on better aws resource management, otherwise we'd run out of resources pretty much immediately in CI

current plan is to add AWS support to test-infra's existing resource manager, boskos

[liztio]

/blocked

[liztio]

Completion on this is blocked on kubernetes/test-infra#10693, but execution is not. Someone else could start working on tests which actually stand up AWS resources to be ready for the aforementioned issue's completion.

[liztio]

/remove-lifecycle active

[ncdc]

@detiber please reassign to @akutz

[detiber]

/assign @akutz

[k8s-ci-robot]

@detiber: GitHub didn't allow me to assign the following users: akutz.

Note that only kubernetes-sigs members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @akutz

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.

[detiber]

/milestone Next

[chuckha]

/close

we can iterate on existing tests now!

[k8s-ci-robot]

@chuckha: Closing this issue.

In response to this:

/close

we can iterate on existing tests now!

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.