Skip to content

Issue with /docs/concepts/services-networking/service/ #3735

@erikbgithub

Description

@erikbgithub

This is a...

  • Feature Request
  • Bug Report
  • Documentation Changerequest

Problem:
The linked page (also here) describes external access to internal services via NodePort. But when I talk to people who really know Kubernetes well they always suggest to externalize services via Ingress. Without this info at the NodePort spot newcomers stop after reading about NodePorts and don't even get to the Ingress page. I mean, who reads the whole manual when one's questions are already (seemingly) answered, right?

Proposed Solution:
The page should mention Ingress, and probably how the Kubernetes stands to the NodePort vs Ingress question. My guess would be that more and more people want Ingresses instead of NodePorts, because they seem to also support other features that is required with externalization like Loadbalancing (which you don't have automatically in bare metal installations).

Page to Update:
https://kubernetes.io/docs/concepts/services-networking/service/

Metadata

Metadata

Assignees

Labels

language/enIssues or PRs related to English languagelifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions