ci: Add kind e2e test

[EnricoMi]

Description

This adds an integration test workflow to the CI running make kind-all and submitting an example job..

This should help to flag issues like #354 early.

Type of change

CI

How Has This Been Tested?

CI

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

[GeorgeJahad]

lgtm

[dejanzele]

I think this is more of an e2e test than an integration one.

[EnricoMi]

renamed

[dejanzele]

I am more in favour of an approach where the test is defined in a bash script, as we can also execute it locally.

[EnricoMi]

I agree, but all this boils down to:

./bin/app/armadactl create queue example
./bin/app/armadactl submit dev/quickstart/example-job.yaml

which is taken from the README.md.

The boilerplate code is hopefully only temporary until #321 is fixed.

[dejanzele]

I don't think #321 will be fixed, as Armada is eventually consistent by design, and clients should handle retries.

[EnricoMi]

would be nice if the armadactl would have an option to wait for the consistency, then users wouldn't need to implement that individually

[dejanzele]

Might be worthwhile opening an Issue in the https://github.com/armadaproject/armada repository.

[EnricoMi]

I have found scripts/e2e-test.sh, moving code there and invoking this from CI.

[EnricoMi]

The existing scripts/e2e-test.sh does not work for me locally and on Github c04d991:
https://github.com/armadaproject/armada-operator/actions/runs/13973241267/job/39120298108?pr=355#step:4:608

Problem is that

make docker-build

produces a docker image that does not work:

$ docker run --rm -it gresearch/armada-operator:v0.5.0-8-g4da5900
exec /armada-operator: no such file or directory

@dejanzele any suggestions?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.37%. Comparing base (6731eb6) to head (7c7abca).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #355   +/-   ##
=======================================
  Coverage   81.37%   81.37%           
=======================================
  Files          16       16           
  Lines        3474     3474           
=======================================
  Hits         2827     2827           
  Misses        452      452           
  Partials      195      195           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dejanzele]

make kind-all installs the latest released Armada Operator Helm chart - https://github.com/armadaproject/armada-operator/blob/main/Makefile#L214
This way we run e2e tests for the latest released Operator, and in case of a change to Operator code or Helm chart, the e2e test won't cover that scenario.

I think it might be better to create a make kind-all-local or edit the make kind-all-dev to build the code and install from the local Helm chart.
That way we would cover the scenario to do an e2e test on current Operator code and on current Helm chart.

[EnricoMi]

Something like this?
561dced#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R218