Skip to content

workflows/ingress: Run basic checks #35683

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

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

pchaigno
Copy link
Member

@pchaigno pchaigno commented Oct 31, 2024

This workflow doesn't run the CLI connectivity tests, so it's missing some basic checks such as unexpected packet drops. This commit adds it.

The check-log-errors test should also be enabled, but it is currently failing because there are errors in logs whenever enabling Ingress. It can be added once those errors are fixed.

@pchaigno pchaigno added release-note/ci This PR makes changes to the CI. feature/k8s-ingress labels Oct 31, 2024
@pchaigno pchaigno force-pushed the pr/pchaigno/ci-ingress-basic-checks branch 2 times, most recently from 489c1b8 to b581aac Compare November 4, 2024 09:21
@pchaigno pchaigno marked this pull request as ready for review November 4, 2024 09:22
@pchaigno pchaigno requested review from a team as code owners November 4, 2024 09:22
@pchaigno pchaigno requested review from sayboras and brlbil November 4, 2024 09:22
Copy link
Member

@sayboras sayboras left a comment

Choose a reason for hiding this comment

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

Thanks ✔️

Copy link
Contributor

@brlbil brlbil left a comment

Choose a reason for hiding this comment

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

We should also add Upload Junits step after Upload artifacts

- name: Upload JUnits [junit]
   if: ${{ always() }}
   uses: actions/upload-artifact@b4b15b8c7c6ac21ea08fcf65892d2ee8f75cf882 # v4.4.3
   with:
      name: cilium-junits-${{ matrix.name }}
      path: cilium-junits/*.xml

and merge-upload job after ingress-conformance-test job
merge-upload job can be same from other workflows

@pchaigno pchaigno force-pushed the pr/pchaigno/ci-ingress-basic-checks branch from b581aac to 9d95c60 Compare November 4, 2024 12:56
@pchaigno
Copy link
Member Author

pchaigno commented Nov 4, 2024

@brlbil Thanks for the review! Seeing this I'm wondering if the JUnit stuff is even needed here, considering we're only going to run 2-3 tests tops (and only one currently). What do we gain from reporting those results via JUnit?

@brlbil
Copy link
Contributor

brlbil commented Nov 4, 2024

@pchaigno Junits are used in reporting tools to list which tests failed with workflow etc... But if you think it is not necessary then by all means remove the --junit* flags.

@pchaigno pchaigno force-pushed the pr/pchaigno/ci-ingress-basic-checks branch from 9d95c60 to 76379d7 Compare November 5, 2024 09:18
This workflow doesn't run the CLI connectivity tests, so it's missing
some basic checks such as unexpected packet drops. This commit adds it.

The check-log-errors test should also be enabled, but it is currently
failing because there are errors in logs whenever enabling Ingress. It
can be added once those errors are fixed.

Signed-off-by: Paul Chaignon <paul.chaignon@gmail.com>
@pchaigno pchaigno force-pushed the pr/pchaigno/ci-ingress-basic-checks branch from 76379d7 to 6a042e5 Compare November 5, 2024 09:20
@pchaigno
Copy link
Member Author

pchaigno commented Nov 5, 2024

@brlbil We discussed it with Tam and the JUnit stuff probably isn't needed here for the time being (probably to be reconsidered if more connectivity tests are covered.)

@pchaigno pchaigno requested a review from brlbil November 5, 2024 09:21
@pchaigno
Copy link
Member Author

pchaigno commented Nov 5, 2024

/test

@pchaigno pchaigno enabled auto-merge November 5, 2024 09:21
Copy link
Contributor

@brlbil brlbil left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@pchaigno pchaigno added this pull request to the merge queue Nov 5, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 5, 2024
Merged via the queue into main with commit 0dc222d Nov 5, 2024
75 checks passed
@pchaigno pchaigno deleted the pr/pchaigno/ci-ingress-basic-checks branch November 5, 2024 10:20
@pchaigno pchaigno added the needs-backport/1.16 This PR / issue needs backporting to the v1.16 branch label Nov 8, 2024
@viktor-kurchenko viktor-kurchenko mentioned this pull request Nov 12, 2024
13 tasks
@viktor-kurchenko viktor-kurchenko added backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. and removed needs-backport/1.16 This PR / issue needs backporting to the v1.16 branch labels Nov 12, 2024
@github-actions github-actions bot added backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. and removed backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. feature/k8s-ingress ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants