Kibana Machine f2ecbf785b [9.0] [Fleet] Fix elastic-agent docker image path (#210008) (#218740) ... # Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] Fix elastic-agent docker image path (#210008)](https://github.com/elastic/kibana/pull/210008) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T21:04:03Z","message":"[Fleet] Fix elastic-agent docker image path (#210008)\n\n## Summary\r\n\r\nStarting in 9.1-SNAPSHOT, the Elastic Agent image has moved from the\r\n`beats` namespace to its own `elastic-agent` namespace in\r\ndocker.elastic.co. This PR updates a few places where the old path is in\r\nuse.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] This was done with a generic find/replace across the Kibana\r\ncodebase. I did not test the changes extensively and made a few changes\r\noutside of the Fleet codebase. Codeowners please be aware.","sha":"6df81592ea0dea55929c0994f9d6915bb24336d5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[Fleet] Fix elastic-agent docker image path ","number":210008,"url":"https://github.com/elastic/kibana/pull/210008","mergeCommit":{"message":"[Fleet] Fix elastic-agent docker image path (#210008)\n\n## Summary\r\n\r\nStarting in 9.1-SNAPSHOT, the Elastic Agent image has moved from the\r\n`beats` namespace to its own `elastic-agent` namespace in\r\ndocker.elastic.co. This PR updates a few places where the old path is in\r\nuse.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] This was done with a generic find/replace across the Kibana\r\ncodebase. I did not test the changes extensively and made a few changes\r\noutside of the Fleet codebase. Codeowners please be aware.","sha":"6df81592ea0dea55929c0994f9d6915bb24336d5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210008","number":210008,"mergeCommit":{"message":"[Fleet] Fix elastic-agent docker image path (#210008)\n\n## Summary\r\n\r\nStarting in 9.1-SNAPSHOT, the Elastic Agent image has moved from the\r\n`beats` namespace to its own `elastic-agent` namespace in\r\ndocker.elastic.co. This PR updates a few places where the old path is in\r\nuse.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] This was done with a generic find/replace across the Kibana\r\ncodebase. I did not test the changes extensively and made a few changes\r\noutside of the Fleet codebase. Codeowners please be aware.","sha":"6df81592ea0dea55929c0994f9d6915bb24336d5"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co>		2025-04-21 22:11:21 +02:00
..
ai-infra/product-doc-artifact-builder	[product doc] adapt for new format of semantic_text field (#206051)	2025-01-13 10:05:16 +01:00
kbn-synthetics-private-location	[9.0] [Fleet] Fix elastic-agent docker image path (#210008) (#218740)	2025-04-21 22:11:21 +02:00