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

Missing ECK network policy for Isolating Elasticsearch Nodes (Ingress 9300) #7833

Open
JM-elastic opened this issue May 21, 2024 · 0 comments
Labels
>docs Documentation

Comments

@JM-elastic
Copy link

JM-elastic commented May 21, 2024

I believe this doc page:
https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s_prerequisites.html

is missing an important network policy that needs to be specified for the "Isolating Elasticsearch" section. The Egress section lists "TCP port 9300 to other Elasticsearch nodes in the namespace (transport port)." but the Ingress section is missing "TCP port 9300 from other Elasticsearch nodes in the namespace (transport port)." The YAML file that's referenced in this section shows an Ingress rule for TCP 9300, but it's not provided in the documentation text.

Thanks,
J.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs Documentation
Projects
None yet
Development

No branches or pull requests

2 participants