Spike: Proxy/Dataplane/Gateway/Kong Gateway naming mess - Githubissues

Kong / kubernetes-ingress-controller

:gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.

https://docs.konghq.com/kubernetes-ingress-controller/

Apache License 2.0

2.2k stars 590 forks source link

Spike: Proxy/Dataplane/Gateway/Kong Gateway naming mess #4732

Open programmer04 opened 11 months ago

programmer04 commented 11 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement

Naming should be consistent for KOng Gateway across docs, logs, codebase, Helm chart, etc. Currently, it is referenced as

proxy (e.g. this is the name of a container with Kong Gateway deployed by Helm)
Kong proxy
Dataplane
gateway
Kong Gateway
etc.

Proposed Solution

decide on consistent naming
implement it everywhere

Additional information

No response

Acceptance Criteria

[ ] Kong Gateway is named consistently across docs, logs, codebase, Helm chart, etc.
[ ] document it somewhere, maybe in Readme.md

mflendrich commented 10 months ago

This needs to be a spike because:

"Gateway" is an overloaded term (Kong Gateway, GWAPI Gateway)
"Control plane" is an overloaded term (hybrid mode CP vs KGO's managed mode CP)
"Dataplane" is likewise overloaded (hybrid mode DP vs KGO's managed mode DP)