Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.x] Fix standalone agent K8s manifest link to include patch level (backport #1344) #1347

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 25, 2024

It was reported in Slack that on the Kubernetes install instructions for standalone agent, customers are being directed to 8.15.2 manifest files before they're fully available.

Essentially this link:

curl -L -O https://raw.githubusercontent.com/elastic/elastic-agent/8.15/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml

Should be:

curl -L -O https://raw.githubusercontent.com/elastic/elastic-agent/8.15.1deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml

I've fixed this by changing the {manifest} variable to include {bare-version} (which is currently set to 8.15.1) rather than {branch} (which is currently set to 8.15).

The screen capture below shows the manifest link as 8.16.0 because this change is going into the main branch. In the public docs, this would be the current patch version, so as I write this that version is currently set to 8.15.1.


Screenshot 2024-09-25 at 11 00 16 AM


This is an automatic backport of pull request #1344 done by [Mergify](https://mergify.com).

* Fix standalone agent K8s manifest link to include patch level

* Update docs/en/ingest-management/elastic-agent/running-on-kubernetes-standalone.asciidoc

Co-authored-by: Julien Mailleret <8582351+jmlrt@users.noreply.github.com>

---------

Co-authored-by: Julien Mailleret <8582351+jmlrt@users.noreply.github.com>
(cherry picked from commit 153b04d)
@mergify mergify bot requested a review from a team as a code owner September 25, 2024 16:25
@mergify mergify bot added the backport label Sep 25, 2024
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@kilfoyle kilfoyle merged commit f459b6d into 8.x Sep 25, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant