Kubernetes的两个Service（ServiceA、ServiceB）和对应的Pod（PodA、PodB）分别属于不同的namespace名称空间，现需要PodA和PodB跨namespace名称空间并通过Service实现互访。应该如何实现？

场景需求

Kubernetes的两个Service（ServiceA、ServiceB）和对应的Pod（PodA、PodB）分别属于不同的namespace名称空间，现需要PodA和PodB跨namespace名称空间并通过Service实现互访。如何实现？

说明：这里是指通过Service的Name进行通信访问，而不是通过Service的IP【因因为每次重启Service，NAME不会改变，而IP是会改变的】。

主机配置规划

服务器名称(hostname)	系统版本	配置	内网IP	外网IP(模拟)
k8s-master	CentOS7.7	2C/4G/20G	172.16.1.110	10.0.0.110
k8s-node01	CentOS7.7	2C/4G/20G	172.16.1.111	10.0.0.111
k8s-node02	CentOS7.7	2C/4G/20G	172.16.1.112	10.0.0.112

创建Service和Pod

相关yaml文件

 [root@k8s-master cross_ns]# pwd

 /root/k8s_practice/cross_ns

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# cat deply_service_myns.yaml

 apiVersion: v1

 kind: Namespace

 metadata:

   name: myns

 ---

 apiVersion: apps/v1

 kind: Deployment

 metadata:

   name: myapp-deploy1

   namespace: myns

 spec:

   replicas:

   selector:

     matchLabels:

       app: myapp

       release: v1

   template:

     metadata:

       labels:

         app: myapp

         release: v1

     spec:

       containers:

       - name: myapp

         image: registry.cn-beijing.aliyuncs.com/google_registry/myapp:v1

         imagePullPolicy: IfNotPresent

         ports:

         - name: http

           containerPort:

 ---

 apiVersion: v1

 kind: Service

 metadata:

   name: myapp-clusterip1

   namespace: myns

 spec:

   type: ClusterIP  # 默认类型

   selector:

     app: myapp

     release: v1

   ports:

   - name: http

     port:

     targetPort: 

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# cat deply_service_mytest.yaml

 apiVersion: v1

 kind: Namespace

 metadata:

   name: mytest

 ---

 apiVersion: apps/v1

 kind: Deployment

 metadata:

   name: myapp-deploy2

   namespace: mytest

 spec:

   replicas:

   selector:

     matchLabels:

       app: myapp

       release: v2

   template:

     metadata:

       labels:

         app: myapp

         release: v2

     spec:

       containers:

       - name: myapp

         image: registry.cn-beijing.aliyuncs.com/google_registry/myapp:v2

         imagePullPolicy: IfNotPresent

         ports:

         - name: http

           containerPort:

 ---

 apiVersion: v1

 kind: Service

 metadata:

   name: myapp-clusterip2

   namespace: mytest

 spec:

   type: ClusterIP  # 默认类型

   selector:

     app: myapp

     release: v2

   ports:

   - name: http

     port:

     targetPort:

运行yaml文件

 kubectl apply -f deply_service_myns.yaml

 kubectl apply -f deply_service_mytest.yaml

查看myns名称空间信息

 [root@k8s-master cross_ns]# kubectl get svc -n myns -o wide

 NAME               TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)   AGE   SELECTOR

 myapp-clusterip1   ClusterIP   10.100.61.11   <none>        /TCP    3m    app=myapp,release=v1

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get deploy -n myns -o wide

 NAME            READY   UP-TO-DATE   AVAILABLE   AGE    CONTAINERS   IMAGES                                                      SELECTOR

 myapp-deploy1   /                            3m7s   myapp        registry.cn-beijing.aliyuncs.com/google_registry/myapp:v1   app=myapp,release=v1

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get rs -n myns -o wide

 NAME                       DESIRED   CURRENT   READY   AGE     CONTAINERS   IMAGES                                                      SELECTOR

 myapp-deploy1-5b9d78576c                            3m15s   myapp        registry.cn-beijing.aliyuncs.com/google_registry/myapp:v1   app=myapp,pod-template-hash=5b9d78576c,release=v1

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get pod -n myns -o wide

 NAME                             READY   STATUS    RESTARTS   AGE     IP             NODE         NOMINATED NODE   READINESS GATES

 myapp-deploy1-5b9d78576c-wfw4n   /     Running             3m20s   10.244.2.136   k8s-node02   <none>           <none>

 myapp-deploy1-5b9d78576c-zsfjl   /     Running             3m20s   10.244.3.193   k8s-node01   <none>           <none>

查看mytest名称空间信息

 [root@k8s-master cross_ns]# kubectl get svc -n mytest -o wide

 NAME               TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE    SELECTOR

 myapp-clusterip2   ClusterIP   10.100.201.103   <none>        /TCP    4m9s   app=myapp,release=v2

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get deploy -n mytest -o wide

 NAME            READY   UP-TO-DATE   AVAILABLE   AGE     CONTAINERS   IMAGES                                                      SELECTOR

 myapp-deploy2   /                            4m15s   myapp        registry.cn-beijing.aliyuncs.com/google_registry/myapp:v2   app=myapp,release=v2

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get rs -n mytest -o wide

 NAME                      DESIRED   CURRENT   READY   AGE     CONTAINERS   IMAGES                                                      SELECTOR

 myapp-deploy2-dc8f96497                            4m22s   myapp        registry.cn-beijing.aliyuncs.com/google_registry/myapp:v2   app=myapp,pod-template-hash=dc8f96497,release=v2

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get pod -n mytest -o wide

 NAME                            READY   STATUS    RESTARTS   AGE     IP             NODE         NOMINATED NODE   READINESS GATES

 myapp-deploy2-dc8f96497-nnkqn   /     Running             4m27s   10.244.3.194   k8s-node01   <none>           <none>

 myapp-deploy2-dc8f96497-w47dt   /     Running             4m27s   10.244.2.137   k8s-node02   <none>           <none>

只看Service和Pod

 [root@k8s-master cross_ns]# kubectl get pod -A -o wide | grep -E '(my)|(NAME)'

 NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE   IP             NODE         NOMINATED NODE   READINESS GATES

 myns                   myapp-deploy1-5b9d78576c-wfw4n               /     Running             41m   10.244.2.136   k8s-node02   <none>           <none>

 myns                   myapp-deploy1-5b9d78576c-zsfjl               /     Running             41m   10.244.3.193   k8s-node01   <none>           <none>

 mytest                 myapp-deploy2-dc8f96497-nnkqn                /     Running             41m   10.244.3.194   k8s-node01   <none>           <none>

 mytest                 myapp-deploy2-dc8f96497-w47dt                /     Running             41m   10.244.2.137   k8s-node02   <none>           <none>

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get svc -A -o wide | grep -E '(my)|(NAME)'

 NAMESPACE              NAME                        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                  AGE   SELECTOR

 myns                   myapp-clusterip1            ClusterIP   10.100.61.11     <none>        /TCP                   41m   app=myapp,release=v1

 mytest                 myapp-clusterip2            ClusterIP   10.100.201.103   <none>        /TCP                   41m   app=myapp,release=v2

pod跨名称空间namespace与Service通信

说明：是通过Service的NAME进行通信，而不是Service的IP【因为每次重启Service，NAME不会改变，而IP是会改变的】。

 # 进入ns名称空间下的一个Pod容器

 [root@k8s-master cross_ns]# kubectl exec -it -n myns myapp-deploy1-5b9d78576c-wfw4n sh

 / # cd /root/

 ### 如下说明在同一名称空间下，通信无问题

 ~ # ping myapp-clusterip1

 PING myapp-clusterip1 (10.100.61.11):  data bytes

  bytes from 10.100.61.11: seq= ttl= time=0.046 ms

  bytes from 10.100.61.11: seq= ttl= time=0.081 ms

 ~ #

 ~ # wget myapp-clusterip1 -O myns.html

 Connecting to myapp-clusterip1 (10.100.61.11:)

 myns.html            %

 ~ #

 ~ # cat myns.html

 Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

 ### 如下说明在不同的名称空间下，通过Service的NAME进行通信存在问题

 ~ # ping myapp-clusterip2

 ping: bad address 'myapp-clusterip2'

 ~ #

 ~ # wget myapp-clusterip2 -O mytest.html

 wget: bad address 'myapp-clusterip2'

实现跨namespace与Service通信

通过Service的ExternalName类型即可实现跨namespace名称空间与Service通信。

Service域名格式：$(service name).$(namespace).svc.cluster.local，其中 cluster.local 为指定的集群的域名

pod跨名称空间namespace与Service通信

到目前所有service和pod信息查看

 [root@k8s-master cross_ns]# kubectl get svc -A -o wide | grep -E '(my)|(NAME)'

 NAMESPACE              NAME                            TYPE           CLUSTER-IP       EXTERNAL-IP                                 PORT(S)                  AGE   SELECTOR

 myns                   myapp-clusterip1                ClusterIP      10.100.61.11     <none>                                      /TCP                   62m   app=myapp,release=v1

 myns                   myapp-clusterip1-externalname   ExternalName   <none>           myapp-clusterip2.mytest.svc.cluster.local   /TCP                   84s   <none>

 mytest                 myapp-clusterip2                ClusterIP      10.100.201.103   <none>                                      /TCP                   62m   app=myapp,release=v2

 mytest                 myapp-clusterip2-externalname   ExternalName   <none>           myapp-clusterip1.myns.svc.cluster.local     /TCP                   84s   <none>

 [root@k8s-master cross_ns]#

 [root@k8s-master cross_ns]# kubectl get pod -A -o wide | grep -E '(my)|(NAME)'

 NAMESPACE              NAME                                         READY   STATUS    RESTARTS   AGE   IP             NODE         NOMINATED NODE   READINESS GATES

 myns                   myapp-deploy1-5b9d78576c-wfw4n               /     Running             62m   10.244.2.136   k8s-node02   <none>           <none>

 myns                   myapp-deploy1-5b9d78576c-zsfjl               /     Running             62m   10.244.3.193   k8s-node01   <none>           <none>

 mytest                 myapp-deploy2-dc8f96497-nnkqn                /     Running             62m   10.244.3.194   k8s-node01   <none>           <none>

 mytest                 myapp-deploy2-dc8f96497-w47dt                /     Running             62m   10.244.2.137   k8s-node02   <none>           <none>

myns 名称空间的pod，访问 mytest 名称空间的Service：myapp-clusterip2

 [root@k8s-master cross_ns]# kubectl exec -it -n myns myapp-deploy1-5b9d78576c-wfw4n sh

 / # cd /root/

 ### 如下说明在同一名称空间下，通信无问题

 ~ # ping myapp-clusterip1

 PING myapp-clusterip1 (10.100.61.11):  data bytes

  bytes from 10.100.61.11: seq= ttl= time=0.057 ms

  bytes from 10.100.61.11: seq= ttl= time=0.071 ms

 ………………

 ~ #

 ~ # wget myapp-clusterip1 -O myns.html

 Connecting to myapp-clusterip1 (10.100.61.11:)

 myns.html            %

 ~ #

 ~ # cat myns.html

 Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

 ### 如下说明通过Service externalname类型，实现了Pod跨namespace名称空间与Service访问

 ~ # ping myapp-clusterip1-externalname

 PING myapp-clusterip1-externalname (10.100.201.103):  data bytes

  bytes from 10.100.201.103: seq= ttl= time=0.050 ms

  bytes from 10.100.201.103: seq= ttl= time=0.311 ms

 ………………

 ~ #

 ~ # wget myapp-clusterip1-externalname -O mytest.html

 Connecting to myapp-clusterip1-externalname (10.100.201.103:)

 mytest.html          %

 ~ #

 ~ # cat mytest.html

 Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>

mytest 名称空间的Pod，访问 myns 名称空间的Service：myapp-clusterip1

 [root@k8s-master cross_ns]# kubectl exec -it -n mytest myapp-deploy2-dc8f96497-w47dt sh

 / # cd /root/

 ### 如下说明在同一名称空间下，通信无问题

 ~ # ping myapp-clusterip2

 PING myapp-clusterip2 (10.100.201.103):  data bytes

  bytes from 10.100.201.103: seq= ttl= time=0.087 ms

  bytes from 10.100.201.103: seq= ttl= time=0.073 ms

 ………………

 ~ #

 ~ # wget myapp-clusterip2 -O mytest.html

 Connecting to myapp-clusterip2 (10.100.201.103:)

 mytest.html          %

 ~ #

 ~ # cat mytest.html

 Hello MyApp | Version: v2 | <a href="hostname.html">Pod Name</a>

 ### 如下说明通过Service externalname类型，实现了Pod跨namespace名称空间与Service访问

 ~ # ping myapp-clusterip2-externalname

 PING myapp-clusterip2-externalname (10.100.61.11):  data bytes

  bytes from 10.100.61.11: seq= ttl= time=0.089 ms

  bytes from 10.100.61.11: seq= ttl= time=0.071 ms

 ………………

 ~ #

 ~ # wget myapp-clusterip2-externalname -O myns.html

 Connecting to myapp-clusterip2-externalname (10.100.61.11:)

 myns.html            %

 ~ #

 ~ # cat myns.html

 Hello MyApp | Version: v1 | <a href="hostname.html">Pod Name</a>

由上可见，实现了Pod跨namespace名称空间与Service访问。

完毕！

———END———
如果觉得不错就关注下呗 (-^O^-) ！

Kubernetes K8S之Pod跨namespace名称空间访问Service服务的更多相关文章

K8S中如何跨namespace 访问服务？为什么ping不通ClusterIP？
1.K8S中如何跨namespace 访问服务? 2.在Pod中为什么ping不通ClusterIP? 简述: Rancher2.0中的一个用户,在K8S环境中,创建两个namespace,对应用进行 ...
pod(一)：Kubernetes(k8s)创建pod的两种方式
目录一.系统环境二.前言三.pod 四.创建pod 4.1 环境介绍 4.2 使用命令行的方式创建pod 4.2.1 创建最简单的pod 4.2.2 创建pod,指定镜像下载策略 4.2.3 创 ...
k8s核心资源之：名称空间（ns）
简介是对一组资源和对象的抽象集合,比如可以用来将系统内部的对象划分为不同的项目组或者用户组. 常见的pod.service.replicaSet和deployment等都是属于某一个namespac ...
简单操作：10分钟实现在kubernetes(k8s)里面部署服务器集群并访问项目（docker三）
前言经过docker安装.k8s开启并登录,我们终于到 "部署k8s服务器集群并访问项目" 这一步了,实现的过程中有太多坑,好在都填平了,普天同庆. 在进行当前课题之前,我们需要 ...
kubernetes 中，Pod、Deployment、ReplicaSet、Service 之间关系分析
deploy控制RS,RS控制Pod,这一整套,向外提供稳定可靠的Service. 详见:https://blog.csdn.net/ucsheep/article/details/81781509
Kubernetes K8S之Service服务详解与示例
K8S之Service概述与代理说明,并详解所有的service服务类型与示例主机配置规划服务器名称(hostname) 系统版本配置内网IP 外网IP(模拟) k8s-master Cent ...
同一个POD中默认共享哪些名称空间
如果通过POD的形式来启动多个容器那么它们的名称空间会是共享的么,所以我这里讨论是在默认情况下同一个POD的不同容器的哪些名称空间是打通的.这里先说一下结论,共享的是UTS.IPC.NET.USER. ...
Kubernetes K8S之鉴权RBAC详解
Kubernetes K8S之鉴权概述与RBAC详解 K8S认证与授权认证「Authentication」认证有如下几种方式: 1.HTTP Token认证:通过一个Token来识别合法用户. H ...
Kubernetes k8s 基于Docker For Windows
开启和安装Kubernetes k8s 基于Docker For Windows 0.最近发现,Docker For Windows Stable在Enable Kubernetes这个问题上 ...

随机推荐

volatile的特性代码验证
一 . 可见性(visibility) volatile关键字修饰的变量,如果值发生了改变,其他线程会立刻获取到,从而避免了出现脏读的情况. public class TestVolatile { p ...
用ps实现提高照片的清晰度
首先通过ctrl+j 拷贝一份然后选择滤镜-->其他-->高反差包留选择叠加,就可以达到效果了,实在不行,多弄几层图层
简述 jpg png gif png-8 png-24 的区别
Gif 格式的特点: 1.透明性,GIF是一种布尔透明类型,既可以是全透明,又可以是不透明,但是不可以半透明: 2.动画 GIF支持动画. 3.无损耗性 GIF是一种无损耗的图像格式,也 ...
Jmeter 常用函数（31）- 详解 __iterationNum
如果你想查看更多 Jmeter 常用函数可以在这篇文章找找哦 https://www.cnblogs.com/poloyy/p/13291704.html 作用获取当前线程的循环次数,跟线程组属性挂 ...
AOP计算方法执行时长
AOP计算方法执行时长依赖引入 <dependency> <groupId>org.springframework.boot</groupId> <arti ...
Magento 2 Factory Objects
In object oriented programming, a factory method is a method that’s used to instantiate an object. F ...
解决使用git，ssh每次都要输入密码
建议:生成ssh 公钥私钥的时候,不要输入密码. 解决方案: 1.修改密码:使用命令 ssh-keygen -p 然后修改密码的时候直接回车,也就是把密码置空. 2.重新生成ssh key, 用 ss ...
启用valgrind的MPI支持
TL;DR sudo apt install valgrind-mpi 内存泄漏和越界问题,是C/C++程序常见问题.有一些工具提供了检测内存泄漏的功能,如 valgrind 的 memchecker ...
区块链入门到实战（34）之Solidity – 变量
Solidity 支持三种类型的变量: 状态变量 – 变量值永久保存在合约存储空间中的变量. 局部变量 – 变量值仅在函数执行过程中有效的变量,函数退出后,变量无效. 全局变量 – 保存在全局命名空间 ...
[转] Linux操作系统启动流程
总启动流程这部分转自:https://www.cnblogs.com/liang-io/p/9651656.html 一般来说,所有的操作系统的启动流程基本就是: 总的来说,linux系统启动流程可 ...

Kubernetes K8S之Pod跨namespace名称空间访问Service服务

场景需求

主机配置规划

创建Service和Pod

pod跨名称空间namespace与Service通信

实现跨namespace与Service通信

pod跨名称空间namespace与Service通信

Kubernetes K8S之Pod跨namespace名称空间访问Service服务的更多相关文章

随机推荐

热门专题