chore: bump kube-stack Helm chart onboarding to 0.9.1#232667
Merged
mykolaharmash merged 3 commits intomainfrom Sep 5, 2025
Merged
chore: bump kube-stack Helm chart onboarding to 0.9.1#232667mykolaharmash merged 3 commits intomainfrom
mykolaharmash merged 3 commits intomainfrom
Conversation
Contributor
|
@rogercoll it makes sense to remove the note added to the instructions #232886. |
Contributor
|
@mykolaharmash @rogercoll should this be reviewed/merged now that the dependency has been resolved? It would be great to include the fix in the next patch release. |
mykolaharmash
approved these changes
Sep 5, 2025
Contributor
mykolaharmash
left a comment
mykolaharmash
left a comment
There was a problem hiding this comment.
Tested locally with Helm v3.18.6 and everything works as expected
mykolaharmash
added
backport:prev-minor
backport:all-open
mykolaharmash
changed the title
Contributor
💔 Build Failed
Failed CI Steps |
Contributor
|
Starting backport for target branches: 8.18, 8.19, 9.0, 9.1 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 5, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> (cherry picked from commit 47cb87b)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 5, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> (cherry picked from commit 47cb87b)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 5, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> (cherry picked from commit 47cb87b)
Contributor
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Sep 5, 2025
…#234207) # Backport This will backport the following commits from `main` to `9.1`: - [chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)](#232667) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Roger Coll","email":"rogercoll@protonmail.com"},"sourceCommit":{"committedDate":"2025-09-05T15:08:14Z","message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"chore: bump kube-stack Helm chart onboarding to 0.9.1","number":232667,"url":"https://github.com/elastic/kibana/pull/232667","mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232667","number":232667,"mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}}]}] BACKPORT--> Co-authored-by: Roger Coll <rogercoll@protonmail.com> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Sep 5, 2025
#234205) # Backport This will backport the following commits from `main` to `8.18`: - [chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)](#232667) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Roger Coll","email":"rogercoll@protonmail.com"},"sourceCommit":{"committedDate":"2025-09-05T15:08:14Z","message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"chore: bump kube-stack Helm chart onboarding to 0.9.1","number":232667,"url":"https://github.com/elastic/kibana/pull/232667","mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232667","number":232667,"mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}}]}] BACKPORT--> Co-authored-by: Roger Coll <rogercoll@protonmail.com> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
shahargl
pushed a commit
to shahargl/kibana
that referenced
this pull request
Sep 7, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
Contributor
Author
|
@mykolaharmash Could we backport to 8.17.x as well? I will merge elastic/elastic-agent#9705 (review) if so |
mykolaharmash
pushed a commit
to mykolaharmash/kibana
that referenced
this pull request
Sep 8, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> (cherry picked from commit 47cb87b) # Conflicts: # x-pack/solutions/observability/plugins/observability_onboarding/public/application/quickstart_flows/otel_kubernetes/otel_kubernetes_panel.tsx
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Sep 8, 2025
#234206) # Backport This will backport the following commits from `main` to `8.19`: - [chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)](#232667) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Roger Coll","email":"rogercoll@protonmail.com"},"sourceCommit":{"committedDate":"2025-09-05T15:08:14Z","message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"chore: bump kube-stack Helm chart onboarding to 0.9.1","number":232667,"url":"https://github.com/elastic/kibana/pull/232667","mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232667","number":232667,"mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}}]}] BACKPORT--> Co-authored-by: Roger Coll <rogercoll@protonmail.com> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
mykolaharmash
added a commit
that referenced
this pull request
Sep 8, 2025
[Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore.
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 8, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore. (cherry picked from commit b43e3bb)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 8, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore. (cherry picked from commit b43e3bb)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 8, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore. (cherry picked from commit b43e3bb)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Sep 8, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore. (cherry picked from commit b43e3bb)
kibanamachine
added a commit
that referenced
this pull request
Sep 8, 2025
…234171) (#234311) # Backport This will backport the following commits from `main` to `8.19`: - [[Oblt Onboarding] Remove note about supported Helm versions (#234171)](#234171) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-09-08T13:08:12Z","message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"[Oblt Onboarding] Remove note about supported Helm versions","number":234171,"url":"https://github.com/elastic/kibana/pull/234171","mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/234171","number":234171,"mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Sep 8, 2025
…34171) (#234313) # Backport This will backport the following commits from `main` to `9.1`: - [[Oblt Onboarding] Remove note about supported Helm versions (#234171)](#234171) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-09-08T13:08:12Z","message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"[Oblt Onboarding] Remove note about supported Helm versions","number":234171,"url":"https://github.com/elastic/kibana/pull/234171","mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/234171","number":234171,"mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Sep 8, 2025
…34171) (#234312) # Backport This will backport the following commits from `main` to `9.0`: - [[Oblt Onboarding] Remove note about supported Helm versions (#234171)](#234171) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-09-08T13:08:12Z","message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"[Oblt Onboarding] Remove note about supported Helm versions","number":234171,"url":"https://github.com/elastic/kibana/pull/234171","mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/234171","number":234171,"mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
kibanamachine
added a commit
that referenced
this pull request
Sep 8, 2025
…234171) (#234310) # Backport This will backport the following commits from `main` to `8.18`: - [[Oblt Onboarding] Remove note about supported Helm versions (#234171)](#234171) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-09-08T13:08:12Z","message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0"],"title":"[Oblt Onboarding] Remove note about supported Helm versions","number":234171,"url":"https://github.com/elastic/kibana/pull/234171","mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/234171","number":234171,"mergeCommit":{"message":"[Oblt Onboarding] Remove note about supported Helm versions (#234171)\n\n[Changes in the\nAgent](elastic/elastic-agent#9535) were released\nand stack version [was bumped in\nKibana](#232667). The snippet now\nworks again with the latest version of Helm and the note is not needed\nanymore.","sha":"b43e3bb8f31469f47c17c3c29c9f849ce5c67e45"}}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
mykolaharmash
added a commit
that referenced
this pull request
Sep 9, 2025
…#234294) # Backport This will backport the following commits from `main` to `9.0`: - [chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)](#232667) <!--- Backport version: 10.0.2 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Roger Coll","email":"rogercoll@protonmail.com"},"sourceCommit":{"committedDate":"2025-09-05T15:08:14Z","message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.2.0","v9.1.4","v8.18.7"],"title":"chore: bump kube-stack Helm chart onboarding to 0.9.1","number":232667,"url":"https://github.com/elastic/kibana/pull/232667","mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/232667","number":232667,"mergeCommit":{"message":"chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667)\n\n## Summary\n\n**Only merge after https://github.com/elastic/elastic-agent/pull/9535\nchanges are released**\n\nNew kube-stack version that fixes CLI issues with Helm 3.18.5+:\nhttps://github.com/open-telemetry/opentelemetry-helm-charts/pull/1809\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>","sha":"47cb87ba81269070d1494afa16c7a604ebc1b935"}},{"branch":"9.1","label":"v9.1.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/234207","number":234207,"state":"MERGED","mergeCommit":{"sha":"220359663e0b91561868b83f864d4f32c1e6643f","message":"[9.1] chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667) (#234207)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.1`:\n- [chore: bump kube-stack Helm chart onboarding to 0.9.1\n(#232667)](https://github.com/elastic/kibana/pull/232667)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Roger Coll <rogercoll@protonmail.com>\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>"}},{"branch":"8.18","label":"v8.18.7","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/234205","number":234205,"state":"MERGED","mergeCommit":{"sha":"0c901caa42f806bebd902049759225d99504cde2","message":"[8.18] chore: bump kube-stack Helm chart onboarding to 0.9.1 (#232667) (#234205)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [chore: bump kube-stack Helm chart onboarding to 0.9.1\n(#232667)](https://github.com/elastic/kibana/pull/232667)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Roger Coll <rogercoll@protonmail.com>\nCo-authored-by: Mykola Harmash <mykola.harmash@gmail.com>"}},{"url":"https://github.com/elastic/kibana/pull/234206","number":234206,"branch":"8.19","state":"OPEN"}]}] BACKPORT--> Co-authored-by: Roger Coll <rogercoll@protonmail.com>
KodeRad
pushed a commit
to KodeRad/kibana
that referenced
this pull request
Sep 15, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
KodeRad
pushed a commit
to KodeRad/kibana
that referenced
this pull request
Sep 15, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore.
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Sep 24, 2025
## Summary **Only merge after elastic/elastic-agent#9535 changes are released** New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Sep 24, 2025
…234171) [Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](elastic#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore.
niros1
pushed a commit
that referenced
this pull request
Sep 30, 2025
[Changes in the Agent](elastic/elastic-agent#9535) were released and stack version [was bumped in Kibana](#232667). The snippet now works again with the latest version of Helm and the note is not needed anymore.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Only merge after elastic/elastic-agent#9535 changes are released
New kube-stack version that fixes CLI issues with Helm 3.18.5+: open-telemetry/opentelemetry-helm-charts#1809
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Identify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.