Skip to content
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

e2e: run release tests on bare metal #865

Merged
merged 6 commits into from
Sep 11, 2024
Merged

e2e: run release tests on bare metal #865

merged 6 commits into from
Sep 11, 2024

Conversation

Freax13
Copy link
Contributor

@Freax13 Freax13 commented Sep 10, 2024

No description provided.

@Freax13 Freax13 requested a review from burgerdev September 10, 2024 07:44
@Freax13 Freax13 requested a review from katexochen as a code owner September 10, 2024 07:44
@Freax13 Freax13 added the no changelog PRs not listed in the release notes label Sep 10, 2024
@Freax13 Freax13 force-pushed the tom/release-test-bm branch from 6183d87 to 6499a8e Compare September 10, 2024 07:46
@katexochen
Copy link
Member

Okay, so it looks like the service type LoadBalancer isn't getting an IP in case of the emoji web service as the port is already taken. Therefore, we are using the WaitForService function to get the ClusterIP instead and wait for the pod to become ready (which we do more explicitly in the normal e2e tests, but here through connecting through the service).

@Freax13 Freax13 force-pushed the tom/release-test-bm branch from 6499a8e to 6cf2edd Compare September 10, 2024 09:29
.github/workflows/release.yml Outdated Show resolved Hide resolved
e2e/internal/kubeclient/deploy.go Show resolved Hide resolved
e2e/release/release_test.go Show resolved Hide resolved
# TODO(burgerdev): cli/genpolicy/assets/allow-all.rego is insecure and deliberately omitted
install -D ${genpolicy.src}/src/kata-opa/allow-all.rego cli/genpolicy/assets/allow-all.rego
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My intent was that we never package an insecure policy in a released binary. Why do we need to package it now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is only needed to run the tests. This commit will be dropped shortly before merging.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This commit will be dropped shortly before merging.

Done

@Freax13 Freax13 force-pushed the tom/release-test-bm branch from 6cf2edd to 84884d7 Compare September 10, 2024 10:49
@Freax13 Freax13 requested a review from burgerdev September 10, 2024 11:22
@Freax13 Freax13 force-pushed the tom/release-test-bm branch from 84884d7 to 7c0eb5c Compare September 11, 2024 06:35
@Freax13 Freax13 merged commit b9f7c7d into main Sep 11, 2024
16 checks passed
@Freax13 Freax13 deleted the tom/release-test-bm branch September 11, 2024 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no changelog PRs not listed in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants