ingress 暴露 TCP 和 UDP 服务

已于 2022-05-13 00:17:16 修改
阅读量2.1k 收藏 5
点赞数 2
分类专栏： Kubernetes ingress 文章标签： tcp/ip udp kubernetes
于 2022-05-13 00:12:33 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_42562106/article/details/124742876
版权

因为是最新ingress 官网推荐使用Kubernetess v1.22以上

# kubectl get node
NAME         STATUS   ROLES                  AGE   VERSION
node91.com   Ready    <none>                 14d   v1.23.6
node93.com   Ready    <none>                 14d   v1.23.6
node94       Ready    control-plane,master   14d   v1.23.6

#打标签(只暴露这两台机)
kubectl label nodes node91.com node92.com storagenode=nginx
ingress暴露前添加以下参数(ingress安装再最下面镜像已替成国内仓库)
#这个就不解释了
hostNetwork: true

#直接匹配标签
nodeSelector:
  storagenode: nginx

TCP暴露

tee tcp-test.yaml<<'-EOF'
apiVersion: v1
kind: ConfigMap
metadata:
  name: tcp-services
  namespace: ingress-nginx
data:
  33333: "default/mysql-primary:3306"
  18080: "default/mygin-v1:80"
EOF

前面是暴露宿主机的33333端口，命名空间+service+端口
33333: "default/mysql-primary:3306"
---------------------------------
# kubectl  get service | grep mysql-primary
mysql-primary                  ClusterIP   10.97.10.111     <none>        3306/TCP
                                                   27h
#客户端测试
# mysql -uroot -p123qwe -h 172.18.4.93 -P33333  
  
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MySQL connection id is 19567
Server version: 8.0.29 Source distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MySQL [(none)]> \s
--------------
mysql  Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1

Connection id:          19567
Current database:
Current user:           root@10.244.1.0
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server:                 MySQL
Server version:         8.0.29 Source distribution
Protocol version:       10
Connection:             172.18.4.93 via TCP/IP
Server characterset:    utf8mb3
Db     characterset:    utf8mb3

再测试一个http的

#还是命名空间+service+端口
18080: "default/mygin-v1:80"
# while true; do curl 172.18.4.93:18080/sys; sleep 0.3; done
hosts:mygin-v1-6c7d88868d-fhm9c
hosts:mygin-v1-6c7d88868d-gsnc4
hosts:mygin-v1-6c7d88868d-x9hlm
hosts:mygin-v1-6c7d88868d-fhm9c
hosts:mygin-v1-6c7d88868d-gsnc4
hosts:mygin-v1-6c7d88868d-x9hlm
hosts:mygin-v1-6c7d88868d-fhm9c

UDP暴露

apiVersion: v1
kind: ConfigMap
metadata:
  name: udp-services
  namespace: ingress-nginx
data:
  53: "kube-system/kube-dns:53"

客户端测试

#换上k8s的dns
# cat /etc/resolv.conf
nameserver 172.18.4.93
客户端解析
# nslookup www.qq.com
Server:         172.18.4.93
Address:        172.18.4.93#53

Non-authoritative answer:
www.qq.com      canonical name = ins-r23tsuuf.ias.tencent-cloud.net.
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 121.14.77.201
Name:   ins-r23tsuuf.ias.tencent-cloud.net
Address: 121.14.77.221

再 172.18.4.93节点上抓

tcpdump -i  ens192 port 53 | grep "qq"

在这里插入图片描述

tee ingress.yaml <<-'EOF'
apiVersion: v1
kind: Namespace
metadata:
  labels:
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
  name: ingress-nginx
---
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx
  namespace: ingress-nginx
---
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
  namespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx
  namespace: ingress-nginx
rules:
- apiGroups:
  - ""
  resources:
  - namespaces
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - configmaps
  - pods
  - secrets
  - endpoints
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - services
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses/status
  verbs:
  - update
- apiGroups:
  - networking.k8s.io
  resources:
  - ingressclasses
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resourceNames:
  - ingress-controller-leader
  resources:
  - configmaps
  verbs:
  - get
  - update
- apiGroups:
  - ""
  resources:
  - configmaps
  verbs:
  - create
- apiGroups:
  - ""
  resources:
  - events
  verbs:
  - create
  - patch
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
  namespace: ingress-nginx
rules:
- apiGroups:
  - ""
  resources:
  - secrets
  verbs:
  - get
  - create
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx
rules:
- apiGroups:
  - ""
  resources:
  - configmaps
  - endpoints
  - nodes
  - pods
  - secrets
  - namespaces
  verbs:
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - nodes
  verbs:
  - get
- apiGroups:
  - ""
  resources:
  - services
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resources:
  - events
  verbs:
  - create
  - patch
- apiGroups:
  - networking.k8s.io
  resources:
  - ingresses/status
  verbs:
  - update
- apiGroups:
  - networking.k8s.io
  resources:
  - ingressclasses
  verbs:
  - get
  - list
  - watch
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
rules:
- apiGroups:
  - admissionregistration.k8s.io
  resources:
  - validatingwebhookconfigurations
  verbs:
  - get
  - update
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx
  namespace: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ingress-nginx
subjects:
- kind: ServiceAccount
  name: ingress-nginx
  namespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
  namespace: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: ingress-nginx-admission
subjects:
- kind: ServiceAccount
  name: ingress-nginx-admission
  namespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: ingress-nginx
subjects:
- kind: ServiceAccount
  name: ingress-nginx
  namespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: ingress-nginx-admission
subjects:
- kind: ServiceAccount
  name: ingress-nginx-admission
  namespace: ingress-nginx
---
apiVersion: v1
data:
  allow-snippet-annotations: "true"
kind: ConfigMap
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-controller
  namespace: ingress-nginx
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-controller
  namespace: ingress-nginx
spec:
  ports:
  - appProtocol: http
    name: http
    port: 80
    protocol: TCP
    targetPort: http
  - appProtocol: https
    name: https
    port: 443
    protocol: TCP
    targetPort: https
  selector:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
  type: NodePort
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-controller-admission
  namespace: ingress-nginx
spec:
  ports:
  - appProtocol: https
    name: https-webhook
    port: 443
    targetPort: webhook
  selector:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
  type: ClusterIP
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-controller
  namespace: ingress-nginx
spec:
  minReadySeconds: 0
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/component: controller
      app.kubernetes.io/instance: ingress-nginx
      app.kubernetes.io/name: ingress-nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/name: ingress-nginx
    spec:
      hostNetwork: true
      containers:
      - args:
        - /nginx-ingress-controller
        - --election-id=ingress-controller-leader
        - --controller-class=k8s.io/ingress-nginx
        - --ingress-class=nginx
        - --configmap=$(POD_NAMESPACE)/ingress-nginx-controller
        - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services
        - --udp-services-configmap=$(POD_NAMESPACE)/udp-services
        - --validating-webhook=:8443
        - --validating-webhook-certificate=/usr/local/certificates/cert
        - --validating-webhook-key=/usr/local/certificates/key
        env:
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: LD_PRELOAD
          value: /usr/local/lib/libmimalloc.so
        image: registry.cn-shenzhen.aliyuncs.com/jbjb/csi:controller-v1.2
        #image: k8s.gcr.io/ingress-nginx/controller:v1.2.0@sha256:d8196e3bc1e72547c5dec66d6556c0ff92a23f6d0919b206be170bc90d5f9185
        imagePullPolicy: IfNotPresent
        lifecycle:
          preStop:
            exec:
              command:
              - /wait-shutdown
        livenessProbe:
          failureThreshold: 5
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: controller
        ports:
        - containerPort: 80
          name: http
          protocol: TCP
        - containerPort: 443
          name: https
          protocol: TCP
        - containerPort: 8443
          name: webhook
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /healthz
            port: 10254
            scheme: HTTP
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          requests:
            cpu: 100m
            memory: 90Mi
        securityContext:
          allowPrivilegeEscalation: true
          capabilities:
            add:
            - NET_BIND_SERVICE
            drop:
            - ALL
          runAsUser: 101
        volumeMounts:
        - mountPath: /usr/local/certificates/
          name: webhook-cert
          readOnly: true
      dnsPolicy: ClusterFirst
      nodeSelector:
        storagenode: nginx
      serviceAccountName: ingress-nginx
      terminationGracePeriodSeconds: 300
      volumes:
      - name: webhook-cert
        secret:
          secretName: ingress-nginx-admission
---
apiVersion: batch/v1
kind: Job
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission-create
  namespace: ingress-nginx
spec:
  template:
    metadata:
      labels:
        app.kubernetes.io/component: admission-webhook
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/part-of: ingress-nginx
        app.kubernetes.io/version: 1.2.0
      name: ingress-nginx-admission-create
    spec:
      containers:
      - args:
        - create
        - --host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.$(POD_NAMESPACE).svc
        - --namespace=$(POD_NAMESPACE)
        - --secret-name=ingress-nginx-admission
        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        image: registry.cn-shenzhen.aliyuncs.com/jbjb/csi:webhook-certgen-v1.1.1
        #image: k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660
        imagePullPolicy: IfNotPresent
        name: create
        securityContext:
          allowPrivilegeEscalation: false
      nodeSelector:
        kubernetes.io/os: linux
      restartPolicy: OnFailure
      securityContext:
        fsGroup: 2000
        runAsNonRoot: true
        runAsUser: 2000
      serviceAccountName: ingress-nginx-admission
---
apiVersion: batch/v1
kind: Job
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission-patch
  namespace: ingress-nginx
spec:
  template:
    metadata:
      labels:
        app.kubernetes.io/component: admission-webhook
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/part-of: ingress-nginx
        app.kubernetes.io/version: 1.2.0
      name: ingress-nginx-admission-patch
    spec:
      containers:
      - args:
        - patch
        - --webhook-name=ingress-nginx-admission
        - --namespace=$(POD_NAMESPACE)
        - --patch-mutating=false
        - --secret-name=ingress-nginx-admission
        - --patch-failure-policy=Fail
        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        image: registry.cn-shenzhen.aliyuncs.com/jbjb/csi:webhook-certgen-v1.1.1
        #image: k8s.gcr.io/ingress-nginx/kube-webhook-certgen:v1.1.1@sha256:64d8c73dca984af206adf9d6d7e46aa550362b1d7a01f3a0a91b20cc67868660
        imagePullPolicy: IfNotPresent
        name: patch
        securityContext:
          allowPrivilegeEscalation: false
      nodeSelector:
        kubernetes.io/os: linux
      restartPolicy: OnFailure
      securityContext:
        fsGroup: 2000
        runAsNonRoot: true
        runAsUser: 2000
      serviceAccountName: ingress-nginx-admission
---
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: nginx
spec:
  controller: k8s.io/ingress-nginx
---
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingWebhookConfiguration
metadata:
  labels:
    app.kubernetes.io/component: admission-webhook
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
    app.kubernetes.io/version: 1.2.0
  name: ingress-nginx-admission
webhooks:
- admissionReviewVersions:
  - v1
  clientConfig:
    service:
      name: ingress-nginx-controller-admission
      namespace: ingress-nginx
      path: /networking/v1/ingresses
  failurePolicy: Fail
  matchPolicy: Equivalent
  name: validate.nginx.ingress.kubernetes.io
  rules:
  - apiGroups:
    - networking.k8s.io
    apiVersions:
    - v1
    operations:
    - CREATE
    - UPDATE
    resources:
    - ingresses
  sideEffects: None
EOF
野猪佩挤
关注
专栏目录
kubernetes 服务发现 ingress
03-11
kubernetes 服务发现 ingress文件
[kubernetes]-ingress开启非80或443的tcp端口
爷来辣的博客
09-05 8860
需求:部分服务不想通过80端口被访问，网关上对80端口有限制，只允许内网访问80和443，所以外网域名必须带端口号访问。以前是直接映射到服务器的端口号，k8s不想通过label指定机子部署。于是研究一下ingress 开启除80和443以外的端口 创建tcp-service.yaml 暴露tcp端口 # tcp-service.yaml apiVersion: v1 kind: Service metadata: name: ingress-nginx namespace: ingress-ngi
SLB不同的监听协议(http或tcp)，导致ingress网关设置http接口的超时时间受限
天草二十六
04-30 747
可以看到，slb设置的监听协议是http的时候，由于slb的默认超时时间是60秒，而它最大只支持180秒。也就是说，http连接的超时时间最大为180秒，这一点和tcp层的超时时间是不同的。所以当你的域名是指向slb，而slb监听的是七层http协议，ingress超时时间的设置是无效的。
浅谈k8s的ingress和service组件关联
Mr_Cuim的博客
08-20 841
简单来说，一个外部request请求会通过ingress匹配至对应的Service，然后通过维护的Endpoint最终流向程序后端pod，从而完成一个完成的http请求。
deploy
小螺号的博客
02-23 440
apiVersion: v1 kind: Namespace metadata: name: ingress-nginx labels: app.kubernetes.io/name: ingress-nginx app.kubernetes.io/instance: ingress-nginx Source: ingress-nginx/templates/controller-serviceaccount.yaml apiVersion: v1 kind: ServiceAccount metadat
【云原生】K8s Ingress rewrite与TCP四层转发讲解与实战操作
匠人精神，持之以恒！
12-10 3788
格式为"。例如下面配置的data第一行表示将default命名空间下的kuard服务的9527端口映射到ingress-controller service的30880端口，即可通过ingress-controller的service ip加30880端口访问到kuard服务。
【kubernetes系列】kubernetes之使用ingress访问TCP和 UDP服务
margu_168的博客
07-20 1550
前面我们通过部署nginx-ingress作为一个访问入口，访问的都是支持http类型的服务，但是某些些场景下我们的服务不支持通过http服务访问，如MySQL，但是MySQL支持通过tcp进行访问。如果通过nodeport方式的话，每个节点都会暴露端口，会显得繁琐浪费。而我们集群一般会部署一个nginx-ingress，我们可以通过它来支持tcp的访问。
k8s ingress配置转发tcp流量
程序猿的博客
04-20 7365
1. 创建tcp-services.yaml文件，内容为下，已mysql为例 apiVersion: v1 kind: ConfigMap metadata: name: tcp-services namespace: ingress-nginx data: 3306: "default/mysql-primary:3306" 2. 创建configmap kubectl create -f tcp-services.yaml # 如果已经存在的话，直接编辑，在data节点下直接添加
使用ingress代理mysql数据库
m0_55441854的博客
08-25 2782
使用ingress代理mysql数据库
K8s+ingress-tcp(mysql)解决方案
完颜振江
01-24 3203
第一部分ingress设置的部分 部署ingress-controller 部署ingress-controller pod及相关资源 先给要部署nginx-ingress的node打上特定标签 [root@k8s-master ]# kubectl label nodes k8s-node1 custom/ingress-controller-ready=true [root@k8s-master ]# kubectl label nodes k8s-node1 custom/ingress-c
ingress-nginx-controller（含镜像和代码）.rar
10-28
ingress-nginx-controller 是 Kubernetes 社区维护的一个项目，它提供了对 Ingress 资源的实现，使得可以通过定义简单的 YAML 文件来管理对外暴露的服务路由。Nginx 作为业界广泛使用的高性能反向代理服务器，其稳定...
K8S对外服务之Ingress
10-10
- `service-nodeport.yaml`则可能定义了一个NodePort类型的Service，它暴露了一个端口，使得外部可以直接通过节点IP和指定端口访问服务。 总的来说，K8S的Ingress允许我们定义基于HTTP的路由规则，实现外部网络到...
ingress-nginx-controller-1.9.yaml
10-18
Nginx Ingress 控制器是广泛应用的一种解决方案，通过配置 Ingress 规则，可以实现基于域名和路径的路由转发，灵活地管理服务的访问策略。本文将深入探讨 ingress-nginx 控制器的安装与使用，以及如何验证其配置是否...
nginx-ingress 日志持久化
03-29
本篇文章将详细探讨Nginx Ingress Controller的日志持久化，以及如何管理和配置这些日志。 首先，Nginx Ingress Controller的日志分为三个主要部分： 1. **Controller日志**：这是控制器自身的日志，包含了其运行...
K8S Ingress-Nginx导出TCP端口
crabdave的博客
12-28 999
K8S Ingress-Nginx导出TCP端口
ingress暴露udp之coredns外部使用
weixin_42562106的博客
06-01 666
coredns 再添加 或者以下方式 修改svc暴露tcp 修改svc暴露udp 客户端配置修改域名IP 测试解析 coredns添加一个域名 测试使用域名访问服务 客户端修改了dns服务器ip 172.18.1.148，直接可以访问
k8s之nginx-ingress做tcp或udp的4层网络负载
zhaikaiyun的博客
12-14 5511
检查nginx-ingress是否开启tcp、udp转发 [test@test02 ingress]$ kubectl get pod -n ingress-nginx -o yaml |grep -i configmap - --configmap=$(POD_NAMESPACE)/nginx-configuration - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services - --udp-services-c...
如何通过 kubernetes ingress 或者 istio ingressgateway 来暴露 TCP 的服务
xcbeyond|疯狂源自梦想，技术成就辉煌
04-08 788
在 kubernetes 或 istio 应用中，一般都是通过 kubernetes ingress 或者 istio ingressgateway 来暴露 HTTP/HTTPS 的服务。但是在实际应用中，还是有不少应用是TCP长连接的，这个是否也是可以通过 ingress 来暴露呢？本文将讲述如何通过 kuberne...
k8s ingress 代理 mysql 3306端口
...
11-07 1098
k8s 使用 ingress 代理 mysql
如何查看一个服务是否已经通过Ingress暴露？
最新发布
09-25
要查看一个服务是否已通过Ingress暴露，你可以按照以下步骤操作： 1. 首先，确认你的Ingress控制器（如Nginx Ingress）是否已成功安装并运行[^1]。通常，使用`kubectl`命令可以检查`ingress-controller`的Pods状态，确保它们处于"Running"状态[^2]。 2. 使用`kubectl`命令获取`Ingress`资源列表，这将显示所有配置好的Ingress及其关联的服务。执行以下命令： ```shell kubectl get ingresses -n <your-namespace> ``` 其中 `<your-namespace>` 是你的Ingress资源所在的工作区名称，比如`ingress-nginx`。 3. 如果看到与你的服务相关的Ingress条目，说明该服务已经被通过Ingress暴露。Ingress会列出路由规则，包括目标端口和服务名，你可以从中判断服务的可访问性。 如果你想要查看某个特定Ingress下的服务映射，可以使用命令： ```shell kubectl describe ingress <ingress-name> -n <namespace> ``` 这将展示详细的Ingress配置，其中包含指向后端服务的路径和端点信息。
评论 5
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值