当前位置： 首页 > news >正文

Kubernetes-ingress

news 来源：原创 2024/9/19 14:29:48

目录

一、部署

1.参考资料：

2.访问架构图：

3.下载yaml文件

4.下载镜像

5.修改后的yaml文件

6.部署ingress-nginx

7.部署成功

二、Ingress HTTP 代理访问

1.yaml文件 

2.部署

3.访问测试

三、Ingress  HTTPS 代理访问

1.创建证书，以及 cert 存储方式

2.yaml文件

3.部署

4.访问测试

四、Nginx 进行 BasicAuth

1.配置认证服务

2.yaml文件

3.部署

4.访问测试

五、Nginx 域名跳转

1.yaml文件

2.部署

3.访问测试

一、部署

1.参考资料：

Ingress-Nginx github 地址：

https://github.com/kubernetes/ingress-nginx

Ingress-Nginx 官方网站：

https://kubernetes.github.io/ingress-nginx/

2.访问架构图：

3.下载yaml文件

源yaml文件下载后，需要修改镜像下载地址

https://github.com/kubernetes/ingress-nginx/blob/controller-v1.9.1/deploy/static/provider/cloud/deploy.yaml

4.下载镜像

docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.9.1
docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen:v20230407

5.修改后的yaml文件

apiVersion: v1
kind: Namespace
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxname: ingress-nginx
---
apiVersion: v1
automountServiceAccountToken: true
kind: ServiceAccount
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginxnamespace: ingress-nginx
---
apiVersion: v1
kind: ServiceAccount
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginxnamespace: ingress-nginx
rules:
- apiGroups:- ""resources:- namespacesverbs:- get
- apiGroups:- ""resources:- configmaps- pods- secrets- endpointsverbs:- get- list- watch
- apiGroups:- ""resources:- servicesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingressesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingresses/statusverbs:- update
- apiGroups:- networking.k8s.ioresources:- ingressclassesverbs:- get- list- watch
- apiGroups:- coordination.k8s.ioresourceNames:- ingress-nginx-leaderresources:- leasesverbs:- get- update
- apiGroups:- coordination.k8s.ioresources:- leasesverbs:- create
- apiGroups:- ""resources:- eventsverbs:- create- patch
- apiGroups:- discovery.k8s.ioresources:- endpointslicesverbs:- list- watch- get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admissionnamespace: ingress-nginx
rules:
- apiGroups:- ""resources:- secretsverbs:- get- create
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx
rules:
- apiGroups:- ""resources:- configmaps- endpoints- nodes- pods- secrets- namespacesverbs:- list- watch
- apiGroups:- coordination.k8s.ioresources:- leasesverbs:- list- watch
- apiGroups:- ""resources:- nodesverbs:- get
- apiGroups:- ""resources:- servicesverbs:- get- list- watch
- apiGroups:- networking.k8s.ioresources:- ingressesverbs:- get- list- watch
- apiGroups:- ""resources:- eventsverbs:- create- patch
- apiGroups:- networking.k8s.ioresources:- ingresses/statusverbs:- update
- apiGroups:- networking.k8s.ioresources:- ingressclassesverbs:- get- list- watch
- apiGroups:- discovery.k8s.ioresources:- endpointslicesverbs:- list- watch- get
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission
rules:
- apiGroups:- admissionregistration.k8s.ioresources:- validatingwebhookconfigurationsverbs:- get- update
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginxnamespace: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: ingress-nginx
subjects:
- kind: ServiceAccountname: ingress-nginxnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admissionnamespace: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: ingress-nginx-admission
subjects:
- kind: ServiceAccountname: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:labels:app.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: ingress-nginx
subjects:
- kind: ServiceAccountname: ingress-nginxnamespace: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission
roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: ingress-nginx-admission
subjects:
- kind: ServiceAccountname: ingress-nginx-admissionnamespace: ingress-nginx
---
apiVersion: v1
data:allow-snippet-annotations: "false"
kind: ConfigMap
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-controllernamespace: ingress-nginx
---
apiVersion: v1
kind: Service
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-controllernamespace: ingress-nginx
spec:externalTrafficPolicy: LocalipFamilies:- IPv4ipFamilyPolicy: SingleStackports:- appProtocol: httpname: httpport: 80protocol: TCPtargetPort: http- appProtocol: httpsname: httpsport: 443protocol: TCPtargetPort: httpsselector:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxtype: LoadBalancer
---
apiVersion: v1
kind: Service
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-controller-admissionnamespace: ingress-nginx
spec:ports:- appProtocol: httpsname: https-webhookport: 443targetPort: webhookselector:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxtype: ClusterIP
---
apiVersion: apps/v1
kind: Deployment
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-controllernamespace: ingress-nginx
spec:minReadySeconds: 0revisionHistoryLimit: 10selector:matchLabels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxstrategy:rollingUpdate:maxUnavailable: 1type: RollingUpdatetemplate:metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1spec:containers:- args:- /nginx-ingress-controller- --publish-service=$(POD_NAMESPACE)/ingress-nginx-controller- --election-id=ingress-nginx-leader- --controller-class=k8s.io/ingress-nginx- --ingress-class=nginx- --configmap=$(POD_NAMESPACE)/ingress-nginx-controller- --validating-webhook=:8443- --validating-webhook-certificate=/usr/local/certificates/cert- --validating-webhook-key=/usr/local/certificates/keyenv:- name: POD_NAMEvalueFrom:fieldRef:fieldPath: metadata.name- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespace- name: LD_PRELOADvalue: /usr/local/lib/libmimalloc.so
#        image: registry.k8s.io/ingress-nginx/controller:v1.9.1@sha256:605a737877de78969493a4b1213b21de4ee425d2926906857b98050f57a95b25image: registry.cn-hangzhou.aliyuncs.com/google_containers/nginx-ingress-controller:v1.9.1imagePullPolicy: IfNotPresentlifecycle:preStop:exec:command:- /wait-shutdownlivenessProbe:failureThreshold: 5httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 1name: controllerports:- containerPort: 80name: httpprotocol: TCP- containerPort: 443name: httpsprotocol: TCP- containerPort: 8443name: webhookprotocol: TCPreadinessProbe:failureThreshold: 3httpGet:path: /healthzport: 10254scheme: HTTPinitialDelaySeconds: 10periodSeconds: 10successThreshold: 1timeoutSeconds: 1resources:requests:cpu: 100mmemory: 90MisecurityContext:allowPrivilegeEscalation: truecapabilities:add:- NET_BIND_SERVICEdrop:- ALLrunAsUser: 101volumeMounts:- mountPath: /usr/local/certificates/name: webhook-certreadOnly: truednsPolicy: ClusterFirstnodeSelector:kubernetes.io/os: linuxserviceAccountName: ingress-nginxterminationGracePeriodSeconds: 300volumes:- name: webhook-certsecret:secretName: ingress-nginx-admission
---
apiVersion: batch/v1
kind: Job
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission-createnamespace: ingress-nginx
spec:template:metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission-createspec:containers:- args:- create- --host=ingress-nginx-controller-admission,ingress-nginx-controller-admission.$(POD_NAMESPACE).svc- --namespace=$(POD_NAMESPACE)- --secret-name=ingress-nginx-admissionenv:- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespace
#        image: registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407@sha256:543c40fd093964bc9ab509d3e791f9989963021f1e9e4c9c7b6700b02bfb227bimage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen:v20230407imagePullPolicy: IfNotPresentname: createsecurityContext:allowPrivilegeEscalation: falsenodeSelector:kubernetes.io/os: linuxrestartPolicy: OnFailuresecurityContext:fsGroup: 2000runAsNonRoot: truerunAsUser: 2000serviceAccountName: ingress-nginx-admission
---
apiVersion: batch/v1
kind: Job
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission-patchnamespace: ingress-nginx
spec:template:metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission-patchspec:containers:- args:- patch- --webhook-name=ingress-nginx-admission- --namespace=$(POD_NAMESPACE)- --patch-mutating=false- --secret-name=ingress-nginx-admission- --patch-failure-policy=Failenv:- name: POD_NAMESPACEvalueFrom:fieldRef:fieldPath: metadata.namespace
#        image: registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407@sha256:543c40fd093964bc9ab509d3e791f9989963021f1e9e4c9c7b6700b02bfb227bimage: registry.cn-hangzhou.aliyuncs.com/google_containers/kube-webhook-certgen:v20230407imagePullPolicy: IfNotPresentname: patchsecurityContext:allowPrivilegeEscalation: falsenodeSelector:kubernetes.io/os: linuxrestartPolicy: OnFailuresecurityContext:fsGroup: 2000runAsNonRoot: truerunAsUser: 2000serviceAccountName: ingress-nginx-admission
---
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:labels:app.kubernetes.io/component: controllerapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: nginx
spec:controller: k8s.io/ingress-nginx
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admissionnamespace: ingress-nginx
spec:egress:- {}podSelector:matchLabels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxpolicyTypes:- Ingress- Egress
---
apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingWebhookConfiguration
metadata:labels:app.kubernetes.io/component: admission-webhookapp.kubernetes.io/instance: ingress-nginxapp.kubernetes.io/name: ingress-nginxapp.kubernetes.io/part-of: ingress-nginxapp.kubernetes.io/version: 1.9.1name: ingress-nginx-admission
webhooks:
- admissionReviewVersions:- v1clientConfig:service:name: ingress-nginx-controller-admissionnamespace: ingress-nginxpath: /networking/v1/ingressesfailurePolicy: FailmatchPolicy: Equivalentname: validate.nginx.ingress.kubernetes.iorules:- apiGroups:- networking.k8s.ioapiVersions:- v1operations:- CREATE- UPDATEresources:- ingressessideEffects: None

6.部署ingress-nginx

kubectl apply -f ingress-nginx-v1.9.1.yaml

7.部署成功

kubectl get all -n ingress-nginx

二、Ingress HTTP 代理访问

拓扑图：

1.yaml文件 

vim deployment-service-ingress-http.yaml
apiVersion: apps/v1
kind: Deployment    #部署一个Deployment控制器
metadata:name: ingress-deploy        #Deployment叫ingress-deploy
spec:replicas: 3        #副本数量2selector:             #标签选择器matchLabels:        #匹配标签name: ingresstemplate:        #模板怎么创建podmetadata:labels:name: ingress    #标签名字为www1spec:containers:        #mainC- name: ingress-nginx    #mainC的名字为ingress-nginximage: nginx:latestimagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: ingress-svc
spec:type: NodePortports:- port: 80targetPort: 80protocol: TCP        #使用TCP协议selector:name: ingress
---
apiVersion: networking.k8s.io/v1
kind: Ingress        #Ingress对象类型
metadata:name: ingressannotations:  nginx.ingress.kubernetes.io/limit-rps: "10"  # 每秒最多处理10个请求  nginx.ingress.kubernetes.io/limit-burst: "5" # 允许超过速率限制的请求数，用于处理突发流量 
spec:ingressClassName: "nginx"    #指定由名为nginx的ingressclass处理请求，kubectl get ingressclass查看rules:- host: www.daboluo.com    #访问的域名是www.daboluo.comhttp:        #http协议paths:- path: /    #指定路径pathType: Prefix  #根据 Kubernetes 版本需求，添加 pathType 字段backend:    service:name: ingress-svc    #如果是nginx路径，后端基于ingress-svc提供（上方的service地址）port: number: 80
#对于 Ingress 资源中的 backend，从 Kubernetes 1.19 开始，应使用新的字段结构，包括 pathType 和对 service 的引用。
#如果告警控制器版本问题，可以使用kubectl explain deploy来查看

2.部署

kubectl apply -f deployment-service-ingress-http.yaml
#查看ingress
kubectl get ingress

3.访问测试

物理机修改hosts文件

C:\Windows\System32\drivers\etc\hosts
192.168.159.82    www.daboluo.com

物理机浏览器访问测试

www.daboluo.com:$nodeport

三、Ingress  HTTPS 代理访问

1.创建证书，以及 cert 存储方式

#创建私钥，输入两次私钥密码
openssl genrsa -des3 -out server.key 2048
#创建当前证书签名请求，输入私钥密码
openssl req -new -key server.key -out server.csr
#私钥备份
cp server.key server.key.org
#给私钥做退密码处理
openssl rsa -in server.key.org -out server.key
#将私钥和请求的证书文件签发为证书
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
mv server.crt tls.crt
mv server.key tls.key
#将tls.crt证书和tls.key私钥封装在名为tls-secret的secret对象里
kubectl create secret tls tls-secret --key tls.key --cert tls.crt

2.yaml文件

vim deployment-svc-ingress-https.yaml
apiVersion: apps/v1
kind: Deployment
metadata:name: ingress-ssl
spec:replicas: 3selector:        #标签选择器matchLabels:    #匹配标签app: ssltemplate:metadata:labels:app: sslspec:containers:- name: nginximage: nginx:latestimagePullPolicy: IfNotPresentports:- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:name: ingress-ssl
spec:type: NodePortports:- port: 8080targetPort: 80protocol: TCPselector:app: ssl
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: ssl.daboluo.comnamespace: defaultannotations:    #元数据信息，是kubernetes集群给第三方应用提供的一种描述机制。kubernetes.io/ingress.class: "nginx"nginx.ingress.kubernetes.io/ssl-redirect: "true"    #强制从http跳转至https。只要写了ingress，上面有这两个标记，就代表开启https访问了，这个信息是读给ingress-nginx去看的。spec:ingressClassName: "nginx"		#指定由名为nginx的ingressclass处理请求，kubectl get ingressclass查看tls:- hosts:- ssl.daboluo.comsecretName: tls-secret    #指定当前tls访问的证书rules:    #客户端规则- host: ssl.daboluo.comhttp:paths:- path: /    #如果访问路径是根路径，后端基于serviceName: ssl提供pathType: Prefix  #根据 Kubernetes 版本需求，添加 pathType 字段backend:service:name: ingress-ssl    #上方servicename的名字port: number: 8080    #service监听的端口

3.部署

kubectl apply -f deployment-svc-ingress-https.yaml
#查看ingress
kubectl get ingress

4.访问测试

物理机添加hosts解析

192.168.159.82 ssl.daboluo.com

浏览器访问：

ssl.daboluo.com:$nodeport#访问http协议已经被强制跳转为https

四、Nginx 进行 BasicAuth

1.配置认证服务

yum -y install httpd-tools
#生成认证文件，这里的文件名必须为auth，后面的用户叫啥无所谓
htpasswd -c auth foo
#将auth文件封装在名为basic-auth的secret镜像里
kubectl create secret generic basic-auth --from-file=auth

2.yaml文件

vim ingress-basic_auth.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: authannotations:nginx.ingress.kubernetes.io/auth-type: basicnginx.ingress.kubernetes.io/auth-secret: basic-authnginx.ingress.kubernetes.io/auth-realm: 'Authentication Required - foo'
spec:ingressClassName: "nginx"		#指定由名为nginx的ingressclass处理请求，kubectl get ingressclass查看rules:- host: auth.daboluo.comhttp:paths:- path: /pathType: Prefixbackend:service:name: ingress-nginx-controllerport:number: 80

3.部署

kubectl apply -f ingress-basic_auth.yaml
#查看ingress
kubectl get ingress#查看svc的nodeport暴露的端口
kubectl get svc

4.访问测试

物理机添加hosts解析

192.168.159.82    auth.daboluo.com

浏览器访问测试：

auth.xinxianghf.com:$nodeport

五、Nginx 域名跳转

1.yaml文件

vim ingress-rew.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:name: rewannotations:nginx.ingress.kubernetes.io/rewrite-target: https://quanmin.baidu.com/v/14846986138098639796
spec:ingressClassName: "nginx"		#指定由名为nginx的ingressclass处理请求，kubectl get ingressclass查看rules:- host: rew.daboluo.com

2.部署

kubectl apply -f ingress-rew.yaml
#查看ingress
kubectl get ingress

3.访问测试

物理机添加hosts解析

192.168.159.82    rew.daboluo.com

浏览器访问：

rew.daboluo.com:$nodeport

相关文章：

  • 北京网站建设多少钱？
  • 辽宁网页制作哪家好_网站建设
  • 高端品牌网站建设_汉中网站制作
  • linux主机间免密登录
  • HBuidlerX 运行到Android App基座时提示没有检测到设备，该如何处理。
  • 002 | 常见的金融量化指标计算
  • Python电商网络数据采集实践||批量数据采集的API接口
  • 使用本地大模型从论文PDF中提取结构化信息
  • 深度学习--数据处理dataloader介绍及代码分析
  • 【C#】一个项目移动了位置，或者换到其他电脑上，编译报错 Files 的值“IGEF，解决方法
  • Elasticsearch 地理查询：高效探索空间数据
  • openstack使用笔记
  • antdv和element表格，假分页+表格高度处理mixins
  • springboot瑜伽课约课小程序-计算机毕业设计源码87936
  • 【数据结构与算法 | 力扣+二叉搜索树篇】力扣450， 98
  • C++中的::
  • 告别DockerHub 镜像下载难题：掌握高效下载策略，畅享无缝开发体验
  • 【Python深度学习】如何实现将将时间序列转换为图像的功能
  • ES6指北【2】—— 箭头函数
  • android图片蒙层
  • cookie和session
  • JavaScript设计模式与开发实践系列之策略模式
  • Java面向对象及其三大特征
  • js操作时间（持续更新）
  • SAP云平台里Global Account和Sub Account的关系
  • swift基础之_对象 实例方法 对象方法。
  • vue：响应原理
  • vuex 笔记整理
  • 创建一种深思熟虑的文化
  • 对象引论
  • 携程小程序初体验
  • 原创：新手布局福音！微信小程序使用flex的一些基础样式属性（一）
  • 主流的CSS水平和垂直居中技术大全
  • zabbix3.2监控linux磁盘IO
  • 智能情侣枕Pillow Talk，倾听彼此的心跳
  • ​2020 年大前端技术趋势解读
  • ​用户画像从0到100的构建思路
  • #考研#计算机文化知识1（局域网及网络互联）
  • #微信小程序（布局、渲染层基础知识）
  • ( 10 )MySQL中的外键
  • (4) openssl rsa/pkey(查看私钥、从私钥中提取公钥、查看公钥)
  • (Matlab)使用竞争神经网络实现数据聚类
  • （Redis使用系列） Springboot 使用redis实现接口Api限流 十
  • （Windows环境）FFMPEG编译，包含编译x264以及x265
  • （二）hibernate配置管理
  • （二）斐波那契Fabonacci函数
  • (附源码)springboot家庭装修管理系统 毕业设计 613205
  • （函数）颠倒字符串顺序（C语言）
  • （七）Flink Watermark
  • （已解决）什么是vue导航守卫
  • （转）总结使用Unity 3D优化游戏运行性能的经验
  • (自适应手机端)行业协会机构网站模板
  • *1 计算机基础和操作系统基础及几大协议
  • .NET 4 并行（多核）“.NET研究”编程系列之二 从Task开始
  • .NET Entity FrameWork 总结 ，在项目中用处个人感觉不大。适合初级用用，不涉及到与数据库通信。
  • .net 按比例显示图片的缩略图
  • .NET建议使用的大小写命名原则
  • .NET开源纪元：穿越封闭的迷雾，拥抱开放的星辰