fix system test for kubernetes integration for k8s v1.27.0

[gsantoro]

What does this PR do?

Fix failing system tests for the integration kubernetes when testing with kubernetes > v1.27.0.

It fails with the following error

[error] failed to initialize Lua VM in /etc/nginx/nginx.conf:47

I tried to just upgrade the version of container image k8s.gcr.io/nginx-slim:0.8 to a newer tag but since I couldn't easily list the tags available (like I would do with docker hub) I couldn't really figure out the Dockerfile related to that image or what was wrong with that image. Questions on stackoverflow about this error seems to suggest that the official image of nginx doesn't come with Lua at all.

Also because of announcement I tried to replace the container registry from k8s.gcr.io to registry.k8s.io but I had a similar problem trying to figure out what was the latest version of nginx image at that container registry.

So the solution was to use an official nginx image from dockerhub. That was enough to fix the issue and make all system tests pass.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• all tests pass on Jenkins

How to test this PR locally

• replicate the Jenkins pipeline locally

Related issues

Screenshots

[constanca-m]

Hey @jsoriano, does merging this commit overwrite the beta versions in Kubernetes package? Beta versions are in 1.40.0 versions as well.

[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-05-26T08:42:47.614+0000

• Duration: 30 min 56 sec

Test stats 🧪

Test	Results
Failed	0
Passed	92
Skipped	0
Total	92

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (0/0)	💚
Files	100.0% (0/0)	💚
Classes	100.0% (0/0)	💚
Methods	96.154% (75/78)	❕
Lines	100.0% (0/0)	💚
Conditionals	100.0% (0/0)	💚

[jsoriano]

Hey @jsoriano, does merging this commit overwrite the beta versions in Kubernetes package? Beta versions are in 1.40.0 versions as well.

The 1.40.0 will be published and beta versions will remain published too. Search requests will start including 1.40.0.

[MichaelKatsoulis]

Why is this line added? Same for the next file

[gsantoro]

it's the output of elastic-package format or elastic-package lint

[MichaelKatsoulis]

strange. Because there is not empty line under all fields. Personally I wouldn't leave this line but it's your choice.

[constanca-m]

You will have to update the K8s package version again since 1.41 exists now.

[gsantoro]

You will have to update the K8s package version again since 1.41 exists now.

Do you mean this PR. It hasn't been merged yet and I haven't got a feedback yet on what's the right naming scheme for beta versions and what comes next. I left a comment at here.

[constanca-m]

You will have to update the K8s package version again since 1.41 exists now.

Do you mean this PR. It hasn't been merged yet and I haven't got a feedback yet on what's the right naming scheme for beta versions and what comes next. I left a comment at here.

You're right, when I saw it was pushed I though it had been committed as well. Sorry, my mistake :)

[elasticmachine]

Package kubernetes - 1.40.0 containing this change is available at https://epr.elastic.co/search?package=kubernetes