大网数据广告活动
服务器运维问答

ingress-nginx: static IP-address for the backend

· 52CE 我爱测

Is that possible to define an ingress ( ingresses.networking.k8s.io ) forwarding requests to a concrete static IP-address in a private network? I have a service that isn't running on a K8S cluster, but it resides in a private net…

问题原文

原帖链接 · Volodymyr Melnyk · CC BY-SA 4.0

Is that possible to define an ingress (ingresses.networking.k8s.io) forwarding requests to a concrete static IP-address in a private network?

I have a service that isn't running on a K8S cluster, but it resides in a private network, and all K8S pods have access to this network. There are many auxiliary services in this network, I don't want to deploy these services in a K8S cluster due to certain reasons. And I'd like to have some of these services exposed via ingress-nginx, but at this time I don't see a way to define the backend as a static IP-address.

Is that possible?

Thanks!

已采纳解答

原帖链接 · Wytrzymały Wiktor · CC BY-SA 4.0

You can use external service as Ingress backend.

You can introduce any external IP address as a Kubernetes service by creating a matching Service and Endpoint object. Then you can use this service as a backend for your Ingress rules.

More details can be found here.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-08-07)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。