Enabling GA release for time_series index.mode

[lalit-satapathy]

We are close to releasing k8 and nginx and the first set of two packages as TSDB GA( in 8.8.0 release). In preparation towards that, creating a draft PR ready.

There is a discussion going on, whether this should be major version change(2.0.0) but not closed yet.

What does this PR do?

Releasing to k8 and nginx as TSDB GA in 8.8 release.

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

How to test this PR locally

Tests being done and tracked separately

Related issues

• Relates #5233

Screenshots

[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-26T12:53:37.876+0000

• Duration: 31 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	114
Skipped	0
Total	114

🤖 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% (2/2)	💚
Files	50.0% (2/4)	👎 -43.75
Classes	50.0% (2/4)	👎 -43.75
Methods	87.179% (102/117)	👎 -1.173
Lines	70.37% (228/324)	👎 -15.555
Conditionals	100.0% (0/0)	💚

[lalit-satapathy]

There is a discussion going on, whether this should be major version change(2.0.0) but not closed yet.

We are deciding to continue with minor version upgrade for now.

[lalit-satapathy]

CC: @mlunadia @ruflin @andresrc for any comments.

[ruflin]

Overall change LGTM. Left some comments that apply to both packages but I would not block the PR on it.

Nit: I would split it up into 2 PR's so in case if issues with 1 package, easier to link to it

[ruflin]

Overall change LGTM. Left some comments that apply to both packages but I would not block the PR on it.

Nit: I would split it up into 2 PR's so in case if issues with 1 package, easier to link to it

[gsantoro]

Do you mind clarifying what is the naming progression convention for versions? I was under the impression that after 1.40.0-beta you would create 1.40.0.

FYI @gizas

[lalit-satapathy]

Good question.. however since there was a discussion(offline) to whether increase major version for this. Lets at-least stick with a minor version increase for now.

[gsantoro]

I have now merged a couple of changes into the kubernetes package.

I now resolved those conflicts for you in this PR. I hope that's ok with you

[lalit-satapathy]

I see that's added as non beta.. hoping that's ok since this PR should follow right after it.

[gsantoro]

My understanding from this comment is that adding a non-beta version after a beta is ok. I'm not sure still what happens with beta versions or what's the naming convention for following beta versions.

[agithomas]

Comments and suggestions added.

Approved. Change looks good to me.

[elasticmachine]

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

[elasticmachine]

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