fix: use supported-versions variables in ceph-api

[mdelapenya]

What does this PR do?

It uses the supported-versions env variables for the ceph-api service in the docker-compose.yml file for the integration.

Why is it important?

It seems values are hardcoded, and that could be affecting the E2E tests.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

Related issues

• Probably caused by 273c6a8
• Relates chore: increase timeout for Ceph e2e-testing#618
• Discovered while testing fix: do not override compose configurations when syncing from beats e2e-testing#630

[mdelapenya]

I'm not sure why this image is version -1 and the regular ceph is -2. @jsoriano could you please 👀 here?

[jsoriano]

I think we wanted to keep using an specific version here, that is different to the one in the ceph service.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Reason: null

• Start Time: 2022-02-03T10:19:34.712+0000

• Duration: 96 min 17 sec

• Commit: 9348ab3

Test stats 🧪

Test	Results
Failed	0
Passed	9464
Skipped	2443
Total	11907

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[jsoriano]

I don't think we can use the same versions in both cases, if I remember well, we kept this here to keep some tests specifically running against some specific older version.

I was wondering how is it possible then that tests pass after the changes in this PR, and I have found that there isn't actually anything using at the moment the ceph-api service. It is not used in the python system tests, and go integration tests are skipped as flaky: #22612

Changes here probably need to be deeper, and maybe not only on the testing side. I think that we need to fix the integration tests and check what system tests are actually testing. Maybe at the end we can use a single ceph service, but we need to make E2E and go integration tests smarter so they know what metricsets they should be using for each versions. This is what the system tests seem to be doing.

Or maybe we can refactor the metricsets so they detect the version and do nothing if they implement collection methods that are not supported. This way we could enable all metricsets with any version. But I'd say that changes in this module have low priority at the moment.

[jsoriano]

I think we wanted to keep using an specific version here, that is different to the one in the ceph service.

[mergify]

This pull request does not have a backport label. Could you fix it @mdelapenya? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[jlind23]

PRs grooming - Closing for now until further updates.