deploy

最新推荐文章于 2024-04-17 15:34:59 发布
最新推荐文章于 2024-04-17 15:34:59 发布
阅读量423 收藏
点赞数
分类专栏： Linux企业实战篇
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/nk298120/article/details/113976226
版权

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
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
name: ingress-nginx
namespace: ingress-nginx

Source: ingress-nginx/templates/controller-configmap.yaml

apiVersion: v1
kind: ConfigMap
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
name: ingress-nginx-controller
namespace: ingress-nginx
data:

Source: ingress-nginx/templates/clusterrole.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
name: ingress-nginx
namespace: ingress-nginx
rules:

  • apiGroups:
    • ‘’
      resources:
    • configmaps
    • endpoints
    • nodes
    • pods
    • secrets
      verbs:
    • list
    • watch
  • apiGroups:
    • ‘’
      resources:
    • nodes
      verbs:
    • get
  • apiGroups:
    • ‘’
      resources:
    • services
      verbs:
    • get
    • list
    • update
    • watch
  • apiGroups:
    • extensions
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingresses
      verbs:
    • get
    • list
    • watch
  • apiGroups:
    • ‘’
      resources:
    • events
      verbs:
    • create
    • patch
  • apiGroups:
    • extensions
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingresses/status
      verbs:
    • update
  • apiGroups:
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingressclasses
      verbs:
    • get
    • list
    • watch

Source: ingress-nginx/templates/clusterrolebinding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
name: ingress-nginx
namespace: ingress-nginx
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: ingress-nginx
subjects:

  • kind: ServiceAccount
    name: ingress-nginx
    namespace: ingress-nginx

Source: ingress-nginx/templates/controller-role.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
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
    • update
    • watch
  • apiGroups:
    • extensions
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingresses
      verbs:
    • get
    • list
    • watch
  • apiGroups:
    • extensions
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingresses/status
      verbs:
    • update
  • apiGroups:
    • networking.k8s.io # k8s 1.14+
      resources:
    • ingressclasses
      verbs:
    • get
    • list
    • watch
  • apiGroups:
    • ‘’
      resources:
    • configmaps
      resourceNames:
    • ingress-controller-leader-nginx
      verbs:
    • get
    • update
  • apiGroups:
    • ‘’
      resources:
    • configmaps
      verbs:
    • create
  • apiGroups:
    • ‘’
      resources:
    • endpoints
      verbs:
    • create
    • get
    • update
  • apiGroups:
    • ‘’
      resources:
    • events
      verbs:
    • create
    • patch

Source: ingress-nginx/templates/controller-rolebinding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
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

Source: ingress-nginx/templates/controller-service-webhook.yaml

apiVersion: v1
kind: Service
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
name: ingress-nginx-controller-admission
namespace: ingress-nginx
spec:
type: ClusterIP
ports:
- name: https-webhook
port: 443
targetPort: webhook
selector:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/component: controller

Source: ingress-nginx/templates/controller-service.yaml

#apiVersion: v1
#kind: Service
#metadata:

labels:

helm.sh/chart: ingress-nginx-2.4.0

app.kubernetes.io/name: ingress-nginx

app.kubernetes.io/instance: ingress-nginx

app.kubernetes.io/version: 0.33.0

app.kubernetes.io/managed-by: Helm

app.kubernetes.io/component: controller

name: ingress-nginx-controller

namespace: ingress-nginx

#spec:

type: NodePort

ports:

- name: http

port: 80

protocol: TCP

targetPort: http

- name: https

port: 443

protocol: TCP

targetPort: https

selector:

app.kubernetes.io/name: ingress-nginx

app.kubernetes.io/instance: ingress-nginx

app.kubernetes.io/component: controller

Source: ingress-nginx/templates/controller-deployment.yaml

apiVersion: apps/v1
kind: DaemonSet
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: controller
name: ingress-nginx-controller
namespace: ingress-nginx
spec:
selector:
matchLabels:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/component: controller
revisionHistoryLimit: 10
minReadySeconds: 0
template:
metadata:
labels:
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/component: controller
spec:
hostNetwork: true
nodeSelector:
kubernetes.io/hostname: server4
dnsPolicy: ClusterFirst
containers:
- name: controller
image: nginx-ingress-controller:0.33.0
imagePullPolicy: IfNotPresent
lifecycle:
preStop:
exec:
command:
- /wait-shutdown
args:
- /nginx-ingress-controller
- --election-id=ingress-controller-leader
- --ingress-class=nginx
- --configmap=ingress-nginx/ingress-nginx-controller
- --validating-webhook=:8443
- --validating-webhook-certificate=/usr/local/certificates/cert
- --validating-webhook-key=/usr/local/certificates/key
securityContext:
capabilities:
drop:
- ALL
add:
- NET_BIND_SERVICE
runAsUser: 101
allowPrivilegeEscalation: true
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
livenessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 3
readinessProbe:
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 3
ports:
- name: http
containerPort: 80
protocol: TCP
- name: https
containerPort: 443
protocol: TCP
- name: webhook
containerPort: 8443
protocol: TCP
volumeMounts:
- name: webhook-cert
mountPath: /usr/local/certificates/
readOnly: true
resources:
requests:
cpu: 100m
memory: 90Mi
serviceAccountName: ingress-nginx
terminationGracePeriodSeconds: 300
volumes:
- name: webhook-cert
secret:
secretName: ingress-nginx-admission

Source: ingress-nginx/templates/admission-webhooks/validating-webhook.yaml

apiVersion: admissionregistration.k8s.io/v1beta1
kind: ValidatingWebhookConfiguration
metadata:
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
name: ingress-nginx-admission
namespace: ingress-nginx
webhooks:

  • name: validate.nginx.ingress.kubernetes.io
    rules:
    • apiGroups:
      • extensions
      • networking.k8s.io
        apiVersions:
      • v1beta1
        operations:
      • CREATE
      • UPDATE
        resources:
      • ingresses
        failurePolicy: Fail
        clientConfig:
        service:
        namespace: ingress-nginx
        name: ingress-nginx-controller-admission
        path: /extensions/v1beta1/ingresses

Source: ingress-nginx/templates/admission-webhooks/job-patch/clusterrole.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: ingress-nginx-admission
annotations:
helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx
rules:

  • apiGroups:
    • admissionregistration.k8s.io
      resources:
    • validatingwebhookconfigurations
      verbs:
    • get
    • update

Source: ingress-nginx/templates/admission-webhooks/job-patch/clusterrolebinding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: ingress-nginx-admission
annotations:
helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: ingress-nginx-admission
subjects:

  • kind: ServiceAccount
    name: ingress-nginx-admission
    namespace: ingress-nginx

Source: ingress-nginx/templates/admission-webhooks/job-patch/job-createSecret.yaml

apiVersion: batch/v1
kind: Job
metadata:
name: ingress-nginx-admission-create
annotations:
helm.sh/hook: pre-install,pre-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx
spec:
template:
metadata:
name: ingress-nginx-admission-create
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
spec:
containers:
- name: create
image: kube-webhook-certgen:v1.2.0
imagePullPolicy: IfNotPresent
args:
- create
- --host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.ingress-nginx.svc
- --namespace=ingress-nginx
- --secret-name=ingress-nginx-admission
restartPolicy: OnFailure
serviceAccountName: ingress-nginx-admission
securityContext:
runAsNonRoot: true
runAsUser: 2000

Source: ingress-nginx/templates/admission-webhooks/job-patch/job-patchWebhook.yaml

apiVersion: batch/v1
kind: Job
metadata:
name: ingress-nginx-admission-patch
annotations:
helm.sh/hook: post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx
spec:
template:
metadata:
name: ingress-nginx-admission-patch
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
spec:
containers:
- name: patch
image: kube-webhook-certgen:v1.2.0
imagePullPolicy: IfNotPresent
args:
- patch
- --webhook-name=ingress-nginx-admission
- --namespace=ingress-nginx
- --patch-mutating=false
- --secret-name=ingress-nginx-admission
- --patch-failure-policy=Fail
restartPolicy: OnFailure
serviceAccountName: ingress-nginx-admission
securityContext:
runAsNonRoot: true
runAsUser: 2000

Source: ingress-nginx/templates/admission-webhooks/job-patch/role.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: ingress-nginx-admission
annotations:
helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx
rules:

  • apiGroups:
    • ‘’
      resources:
    • secrets
      verbs:
    • get
    • create

Source: ingress-nginx/templates/admission-webhooks/job-patch/rolebinding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: ingress-nginx-admission
annotations:
helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
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

Source: ingress-nginx/templates/admission-webhooks/job-patch/serviceaccount.yaml

apiVersion: v1
kind: ServiceAccount
metadata:
name: ingress-nginx-admission
annotations:
helm.sh/hook: pre-install,pre-upgrade,post-install,post-upgrade
helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
labels:
helm.sh/chart: ingress-nginx-2.4.0
app.kubernetes.io/name: ingress-nginx
app.kubernetes.io/instance: ingress-nginx
app.kubernetes.io/version: 0.33.0
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/component: admission-webhook
namespace: ingress-nginx

HTDST
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
【云原生】K8s Ingress rewrite与TCP四层转发讲解与实战操作
匠人精神，持之以恒！
12-10 3604
格式为"。例如下面配置的data第一行表示将default命名空间下的kuard服务的9527端口映射到ingress-controller service的30880端口，即可通过ingress-controller的service ip加30880端口访问到kuard服务。
k8s ingress配置转发tcp流量
程序猿的博客
04-20 6860
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节点下直接添加
K8S 部署 logstash 解析 nginx log 接入ELK_logstash-8
最新发布
2401_83944596的博客
04-17 988
sincedb_path => “自定义位置” # 此参数记录了读取日志的位置，默认在 data/plugins/inputs/file/.sincedb*16、mysql的innodb如何定位锁问题，mysql如何减少主从复制延迟?2、在工作中，运维人员经常需要跟运营人员打交道，请问运营人员是做什么工作的?6、Squid、Varinsh和Nginx有什么区别，工作中你怎么选择?5、LVS、Nginx、HAproxy有什么区别?7、Tomcat和Resin有什么区别，工作中你怎么选择?
ingress 暴露 TCP 和 UDP 服务
weixin_42562106的博客
05-13 1889
#打标签(只暴露这两台机) kubectl label nodes node91.com node92.com storagenode=nginx ingress暴露前添加以下参数(安装再最下面镜像已经替换好) #这个就不解释了 hostNetwork: true #直接匹配标签 nodeSelector: storagenode: nginx TCP暴露 tee tcp-test.yaml<<'-EOF' apiVersion: v1 kind: ConfigMap metadata
使用ingress代理mysql数据库
m0_55441854的博客
08-25 2548
使用ingress代理mysql数据库
K8s+ingress-tcp(mysql)解决方案
完颜振江
01-24 2988
第一部分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
PDQ Deploy 19.0.40.rar
07-15
PDQ Deploy 是一款功能强大的软件部署工具，它允许系统管理员将几乎任何应用程序或补丁同时安装到多台Windows计算机上，PDQ部署节省时间和精力，使管理员能够轻松地在网络上安装，卸载，更新，修复或进行许多其他...
【kubernetes系列】kubernetes之使用ingress访问TCP和 UDP服务
margu_168的博客
07-20 1157
前面我们通过部署nginx-ingress作为一个访问入口，访问的都是支持http类型的服务，但是某些些场景下我们的服务不支持通过http服务访问，如MySQL，但是MySQL支持通过tcp进行访问。如果通过nodeport方式的话，每个节点都会暴露端口，会显得繁琐浪费。而我们集群一般会部署一个nginx-ingress，我们可以通过它来支持tcp的访问。
[kubernetes]-ingress开启非80或443的tcp端口
爷来辣的博客
09-05 8216
需求:部分服务不想通过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
K8S Ingress-Nginx导出TCP端口
alksjdfp32r的博客
12-28 831
K8S Ingress-Nginx导出TCP端口
ingress nginx基于域名的网络转发资源
weixin_46837396的博客
08-25 2456
一、Ingress介绍 在前面课程中已经提到，Service对集群之外暴露服务的主要方式有两种：NotePort和LoadBalancer，但是这两种方式，都有一定的缺点： # NodePort方式的缺点是会占用很多集群机器的端口，那么当集群服务变多的时候，这个缺点就愈发明显 # LB方式的缺点是每个service需要一个LB，浪费、麻烦，并且需要kubernetes之外设备的支持 基于这种现状，kubernetes提供了Ingress资源对象，Ingress只需要一个NodePort或者一个LB就
Kubernetes中的nodePort，targetPort，port的区别和意义(转)
weixin_30363981的博客
04-19 218
原文https://blog.csdn.net/u013760355/article/details/70162242 https://blog.csdn.net/xinghun_4/article/details/50492041 1. nodePort 　外部机器可访问的端口。 比如一个Web应用需要被其他用户访问，那么需要配置type=NodePort，而且配置nodePort=3...
Kubernetes_11_Ingress服务暴露
05-05 371
Ingress 服务暴露 Ingress 是K8s API 的标准资源类型之一，也是一种核心资源，它其实就是一级基于域名和URL路径，把用户的请求转发至指定Service资源的规则。 可以将集群外部的请求流量，转发到集群内部，从而实现服务暴露。 说白了，Ingress就是个nginx +一段go 脚本而已。 常用的Ingress 控制器实现: Ingress-nginx HAProxy Traefik : 这里使用这个作为服务暴露 traefik 官网地址: https://doc.traefik.io
如何通过 kubernetes ingress 或者 istio ingressgateway 来暴露 TCP 的服务
xcbeyond|疯狂源自梦想，技术成就辉煌
04-08 707
在 kubernetes 或 istio 应用中，一般都是通过 kubernetes ingress 或者 istio ingressgateway 来暴露 HTTP/HTTPS 的服务。但是在实际应用中，还是有不少应用是TCP长连接的，这个是否也是可以通过 ingress 来暴露呢？本文将讲述如何通过 kuberne...
使用ingress暴露服务时候，kubectl apply -f ingress-rule.yaml 报错：error when creating “ingress-rule.yaml“: Inter
weixin_42188778的博客
09-20 944
Error from server (InternalError): error when creating "ingress-rule.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1beta1/in
k8s中通过ingress暴露多端口deployment
novice的博客
03-13 1559
项目中有一个notify微服务，业务逻辑上，需要在web界面上操作发送模板（微服务）、和推送（websocket），因此需要将后端的微服务和websocket同时对外暴露，前端web界面操作时需要走外网，同时实现微服务内部之间和notify访问，仍然走内网。
阿里云通过nginx-ingress-controller 暴露服务
xiojing的博客
07-28 2735
本文有参考：阿里云的文档：https://developer.aliyun.com/article/721569。然后参考对照实际部署的k8s集群。梳理部署在k8s的不同应用如何在公网被不同的域名访问到。 理解： 实际nginx-ingress-controller 就是在k8s集群中创建一个具有类似nginx作用的应用。此nginx 应用负责接受所有来自不同域名的请求，然后根据不同ingress 定义的规则转发到对应的service。 看一下nginx-ingress service apiV.
k8s 中 ingress的安装及配置
bjsunwei的博客
12-22 2301
ingress 服务在k8s中也是以后台pod的形式存在，需要安装nginx-ingress-controller的镜像。 需要单独建立ingress的service，防火墙上发布应用，针对的是次service的端口。 ingress上发布应用，需要新增单独的ingress配置，配置域名、端口、后台对应的service
Linux Deploy
03-20
Linux Deploy是一个在Android设备上运行Linux发行版的应用程序。它允许用户将Linux系统安装到Android设备上，并在设备上运行Linux应用程序和命令。使用Linux Deploy，用户可以选择不同的Linux发行版，如Ubuntu、...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值