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

[DOCS] Enroll additional nodes on Docker #81787

Merged

Conversation

lockewritesdocs
Copy link
Contributor

@lockewritesdocs lockewritesdocs commented Dec 15, 2021

Adds a new section for enrolling additional nodes on Docker when starting a single-node, secured Elasticsearch cluster.

Preview link: https://elasticsearch_81787.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/docker.html#_enroll_additional_nodes

Apply these changes to the Stack docs

This section will be added to starting a single node cluster on Docker in the Stack docs through elastic/stack-docs#1922.

@lockewritesdocs lockewritesdocs added >docs General docs changes :Security/TLS SSL/TLS, Certificates v8.0.0 auto-backport-and-merge Automatically create backport pull requests and merge when ready v8.1.0 labels Dec 15, 2021
@lockewritesdocs lockewritesdocs self-assigned this Dec 15, 2021
@elasticmachine elasticmachine added Team:Security Meta label for security team Team:Docs Meta label for docs team labels Dec 15, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

Copy link
Contributor

@bytebilly bytebilly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we should use es01 and es02 as the default name for nodes, like we do in other places.

docs/reference/setup/install/docker.asciidoc Outdated Show resolved Hide resolved
Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>
@lockewritesdocs
Copy link
Contributor Author

I'm wondering if we should use es01 and es02 as the default name for nodes, like we do in other places.

@bytebilly, I'll make those changes to align with our other Docker docs in the Stack 👍

@lockewritesdocs lockewritesdocs merged commit dd47e68 into elastic:master Dec 16, 2021
@lockewritesdocs lockewritesdocs deleted the docs__docker-enroll-nodes branch December 16, 2021 17:42
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.0

lockewritesdocs pushed a commit to lockewritesdocs/elasticsearch that referenced this pull request Dec 16, 2021
* [DOCS] Enroll additional nodes on Docker

* Remove -p option for second node

Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>

* Rename nodes to align with other Docker docs

* Add elastic network to first node docker run command

* Remove hyphen from node names

Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>
elasticsearchmachine pushed a commit that referenced this pull request Dec 16, 2021
* [DOCS] Enroll additional nodes on Docker

* Remove -p option for second node

Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>

* Rename nodes to align with other Docker docs

* Add elastic network to first node docker run command

* Remove hyphen from node names

Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>

Co-authored-by: Fabio Busatto <52658645+bytebilly@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport-and-merge Automatically create backport pull requests and merge when ready >docs General docs changes :Security/TLS SSL/TLS, Certificates Team:Docs Meta label for docs team Team:Security Meta label for security team v8.0.0-rc1 v8.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants