Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@magicMirror has nothing to do with K8S specifically, rather with the _container_ or in K8S pod.
Question was: Should the container (pod) use host based routing?
As in being aware of which specific domain / host the container runs and utilize it? -
@IntrusionCM why? Just use your WAF or stick a reverse proxy between it and your containers.
It also might help to know if this is for cloud or VM. -
@sariel the question why is my question, I'm curious and wanted to have a discussion.
You know with arguments and kinky stuff like explanations and full sentences... -
@IntrusionCM
If you are working in a k8s context, and using an ingress, then the host based routing is done there, in a single responsibility approach.
Do your containers needs to be aware of the host - and base thier request handling logic on that?
Related Rants
Scaling....
A question or more discussion / looking for feedback.
Let's say we have
Application Firewall
- Application Routing
-- API Gateway
Then lots of containers.
Would you use host based routing in the containers?
It seems wrong to me, as in my opinion it breaks the boundary the API gateway provides.
Maybe someone can share his experience, I'd be delighted.
question
host based routing
scaling
api gateway