ironbank: move to ubi9

[v1v]

What does this PR do?

#3567 partially changed the ubi version to ubi9 but there were some other changes required in the packaging itself and the base docker images.

Why is it important?

ubi9 is not available yet.

Test

It ran in the CI

$ docker pull docker.elastic.co/observability-ci/elastic-agent-ubi9:52773d50b4496e1e2d5ba82736c69aa7862161e8
$ docker inspect docker.elastic.co/observability-ci/elastic-agent-ubi9:52773d50b4496e1e2d5ba82736c69aa7862161e8 | jq -r '.[0].Config.Labels' | grep ubi
  "com.redhat.component": "ubi9-minimal-container",

In addition

$ wget https://storage.googleapis.com/fleet-ci-artifacts/elastic-agent/commits/52773d50b4496e1e2d5ba82736c69aa7862161e8/elastic-agent-ironbank-8.12.0-SNAPSHOT-docker-build-context.tar.gz
$ tar xvzf elastic-agent-ironbank-8.12.0-SNAPSHOT-docker-build-context.tar.gz
x ./
x Dockerfile
x LICENSE
x README.md
x config
x config/docker-entrypoint
x hardening_manifest.yaml
$ grep -R ubi
./Dockerfile:ARG BASE_IMAGE=redhat/ubi/ubi9
./hardening_manifest.yaml:  BASE_IMAGE: "redhat/ubi/ubi9"

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/fragments using the changelog tool
• I have added an integration test or an E2E test

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[v1v]

/package

[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

• Start Time: 2023-11-03T10:45:16.471+0000

• Duration: 82 min 57 sec

Test stats 🧪

Test	Results
Failed	0
Passed	4941
Skipped	57
Total	4998

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

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

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[v1v]

/package

[v1v]

/test

[v1v]

@elastic/ingest-eng-prod , do you happen to know what's the reason for those errors in Buildkite? It seems they are also failing in the main branch but I'm afraid I cannot find what's the reason for those errors

[elastic-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[pierrehilbert]

It's green now ;-)

[pierrehilbert]

Thx!