使用ingress nginx代理grpc

最新推荐文章于 2024-04-22 09:23:39 发布
最新推荐文章于 2024-04-22 09:23:39 发布
阅读量2.5k 收藏 3
点赞数
分类专栏： kubernetes
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/cyxinda/article/details/107956079
版权

使用ingress nginx代理grpc

使用ingress代理dgraph grpc服务

最近在使用图数据库dgraph，开始选择使用k8s拉起整个图数据库，使用ingress nginx代理grpc端口，别问我为什么使用grpc服务，是因为dgraph-io/dgraph4j使用的就是grpc协议。

搭建dgraph服务

使用官方文档中的yaml，直接拉起

# This highly available config creates 3 Dgraph Zeros, 3 Dgraph
# Alphas with 3 replicas, and 1 Ratel UI client. The Dgraph cluster
# will still be available to service requests even when one Zero
# and/or one Alpha are down.
#
# There are 3 services can can be used to expose outside the cluster as needed:
#       dgraph-zero-public - To load data using Live & Bulk Loaders
#       dgraph-alpha-public - To connect clients and for HTTP APIs
#       dgraph-ratel-public - For Dgraph UI
apiVersion: v1
kind: Namespace
metadata:
  name: dgraph
---
apiVersion: v1
kind: Service
metadata:
  name: dgraph-zero-public
  namespace: dgraph
  labels:
    app: dgraph-zero
    monitor: zero-dgraph-io
spec:
  type: ClusterIP
  ports:
  - port: 5080
    targetPort: 5080
    name: grpc-zero
  - port: 6080
    targetPort: 6080
    name: http-zero
  selector:
    app: dgraph-zero
---
apiVersion: v1
kind: Service
metadata:
  name: dgraph-alpha-public
  namespace: dgraph
  labels:
    app: dgraph-alpha
    monitor: alpha-dgraph-io
spec:
  type: NodePort
  ports:
  - port: 8080
    targetPort: 8080
    name: http-alpha
    nodePort: 32678
  - port: 9080
    targetPort: 9080
    name: grpc-alpha
  selector:
    app: dgraph-alpha
---
apiVersion: v1
kind: Service
metadata:
  name: dgraph-ratel-public
  namespace: dgraph
  labels:
    app: dgraph-ratel
spec:
  type: ClusterIP
  ports:
  - port: 8000
    targetPort: 8000
    name: http-ratel
  selector:
    app: dgraph-ratel
---
# This is a headless service which is necessary for discovery for a dgraph-zero StatefulSet.
# https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#creating-a-statefulset
apiVersion: v1
kind: Service
metadata:
  name: dgraph-zero
  namespace: dgraph
  labels:
    app: dgraph-zero
spec:
  ports:
  - port: 5080
    targetPort: 5080
    name: grpc-zero
  clusterIP: None
  # We want all pods in the StatefulSet to have their addresses published for
  # the sake of the other Dgraph Zero pods even before they're ready, since they
  # have to be able to talk to each other in order to become ready.
  publishNotReadyAddresses: true
  selector:
    app: dgraph-zero
---
# This is a headless service which is necessary for discovery for a dgraph-alpha StatefulSet.
# https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#creating-a-statefulset
apiVersion: v1
kind: Service
metadata:
  name: dgraph-alpha
  namespace: dgraph
  labels:
    app: dgraph-alpha
spec:
  ports:
  - port: 7080
    targetPort: 7080
    name: grpc-alpha-int
  clusterIP: None
  # We want all pods in the StatefulSet to have their addresses published for
  # the sake of the other Dgraph alpha pods even before they're ready, since they
  # have to be able to talk to each other in order to become ready.
  publishNotReadyAddresses: true
  selector:
    app: dgraph-alpha
---
# This StatefulSet runs 3 Dgraph Zero.
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: dgraph-zero
  namespace: dgraph
spec:
  serviceName: "dgraph-zero"
  replicas: 3
  selector:
    matchLabels:
      app: dgraph-zero
  template:
    metadata:
      labels:
        app: dgraph-zero
    spec:
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 100
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - dgraph-zero
              topologyKey: kubernetes.io/hostname
      containers:
      - name: zero
        image: dgraph/dgraph:latest
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 5080
          name: grpc-zero
        - containerPort: 6080
          name: http-zero
        volumeMounts:
        - name: datadir
          mountPath: /dgraph
        env:
          - name: POD_NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
        command:
          - bash
          - "-c"
          - |
            set -ex
            [[ `hostname` =~ -([0-9]+)$ ]] || exit 1
            ordinal=${BASH_REMATCH[1]}
            idx=$(($ordinal + 1))
            if [[ $ordinal -eq 0 ]]; then
              exec dgraph zero --my=$(hostname -f):5080 --idx $idx --replicas 3
            else
              exec dgraph zero --my=$(hostname -f):5080 --peer dgraph-zero-0.dgraph-zero.${POD_NAMESPACE}.svc.cluster.local:5080 --idx $idx --replicas 3
            fi
        livenessProbe:
          httpGet:
            path: /health
            port: 6080
          initialDelaySeconds: 15
          periodSeconds: 10
          timeoutSeconds: 5
          failureThreshold: 6
          successThreshold: 1
        readinessProbe:
          httpGet:
            path: /health
            port: 6080
          initialDelaySeconds: 15
          periodSeconds: 10
          timeoutSeconds: 5
          failureThreshold: 6
          successThreshold: 1
      terminationGracePeriodSeconds: 60
      volumes:
      - name: datadir
        persistentVolumeClaim:
          claimName: datadir
  updateStrategy:
    type: RollingUpdate
  volumeClaimTemplates:
  - metadata:
      name: datadir
      annotations:
        volume.alpha.kubernetes.io/storage-class: ceph-sc
    spec:
      storageClassName: ceph-sc
      accessModes:
        - "ReadWriteOnce"
      resources:
        requests:
          storage: 5Gi
---
# This StatefulSet runs 3 replicas of Dgraph Alpha.
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: dgraph-alpha
  namespace: dgraph
spec:
  serviceName: "dgraph-alpha"
  replicas: 3
  selector:
    matchLabels:
      app: dgraph-alpha
  template:
    metadata:
      labels:
        app: dgraph-alpha
    spec:
      affinity:
        podAntiAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - weight: 100
            podAffinityTerm:
              labelSelector:
                matchExpressions:
                - key: app
                  operator: In
                  values:
                  - dgraph-alpha
              topologyKey: kubernetes.io/hostname
      # Initializing the Alphas:
      #
      # You may want to initialize the Alphas with data before starting, e.g.
      # with data from the Dgraph Bulk Loader: https://dgraph.io/docs/deploy/#bulk-loader.
      # You can accomplish by uncommenting this initContainers config. This
      # starts a container with the same /dgraph volume used by Alpha and runs
      # before Alpha starts.
      #
      # You can copy your local p directory to the pod's /dgraph/p directory
      # with this command:
      #
      #    kubectl cp path/to/p dgraph-alpha-0:/dgraph/ -c init-alpha
      #    (repeat for each alpha pod)
      #
      # When you're finished initializing each Alpha data directory, you can signal
      # it to terminate successfully by creating a /dgraph/doneinit file:
      #
      #    kubectl exec dgraph-alpha-0 -c init-alpha touch /dgraph/doneinit
      #
      # Note that pod restarts cause re-execution of Init Containers. Since
      # /dgraph is persisted across pod restarts, the Init Container will exit
      # automatically when /dgraph/doneinit is present and proceed with starting
      # the Alpha process.
      #
      # Tip: StatefulSet pods can start in parallel by configuring
      # .spec.podManagementPolicy to Parallel:
      #
      #     https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#deployment-and-scaling-guarantees
      #
      # initContainers:
      #   - name: init-alpha
      #     image: dgraph/dgraph:latest
      #     command:
      #       - bash
      #       - "-c"
      #       - |
      #         trap "exit" SIGINT SIGTERM
      #         echo "Write to /dgraph/doneinit when ready."
      #         until [ -f /dgraph/doneinit ]; do sleep 2; done
      #     volumeMounts:
      #       - name: datadir
      #         mountPath: /dgraph
      containers:
      - name: alpha
        image: dgraph/dgraph:latest
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 7080
          name: grpc-alpha-int
        - containerPort: 8080
          name: http-alpha
        - containerPort: 9080
          name: grpc-alpha
        volumeMounts:
        - name: datadir
          mountPath: /dgraph
        env:
          # This should be the same namespace as the dgraph-zero
          # StatefulSet to resolve a Dgraph Zero's DNS name for
          # Alpha's --zero flag.
          - name: POD_NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
        # dgraph versions earlier than v1.2.3 and v20.03.0 can only support one zero:
        #  `dgraph alpha --zero dgraph-zero-0.dgraph-zero.${POD_NAMESPACE}.svc.cluster.local:5080`
        # dgraph-alpha versions greater than or equal to v1.2.3 or v20.03.1 can support
        #  a comma-separated list of zeros.  The value below supports 3 zeros
        #  (set according to number of replicas)
        command:
          - bash
          - "-c"
          - |
            set -ex
            dgraph alpha --my=$(hostname -f):7080 --whitelist 10.2.0.0/16,192.168.0.0/16 --lru_mb 2048 --zero dgraph-zero-0.dgraph-zero.${POD_NAMESPACE}.svc.cluster.local:5080,dgraph-zero-1.dgraph-zero.${POD_NAMESPACE}.svc.cluster.local:5080,dgraph-zero-2.dgraph-zero.${POD_NAMESPACE}.svc.cluster.local:5080
        livenessProbe:
          httpGet:
            path: /health?live=1
            port: 8080
          initialDelaySeconds: 15
          periodSeconds: 10
          timeoutSeconds: 5
          failureThreshold: 6
          successThreshold: 1
        readinessProbe:
          httpGet:
            path: /health
            port: 8080
          initialDelaySeconds: 15
          periodSeconds: 10
          timeoutSeconds: 5
          failureThreshold: 6
          successThreshold: 1
      terminationGracePeriodSeconds: 600
      volumes:
      - name: datadir
        persistentVolumeClaim:
          claimName: datadir
  updateStrategy:
    type: RollingUpdate
  volumeClaimTemplates:
  - metadata:
      name: datadir
      annotations:
        volume.alpha.kubernetes.io/storage-class: ceph-sc
    spec:
      storageClassName: ceph-sc
      accessModes:
        - "ReadWriteOnce"
      resources:
        requests:
          storage: 5Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: dgraph-ratel
  namespace: dgraph
  labels:
    app: dgraph-ratel
spec:
  selector:
    matchLabels:
      app: dgraph-ratel
  template:
    metadata:
      labels:
        app: dgraph-ratel
    spec:
      containers:
      - name: ratel
        image: dgraph/dgraph:latest
        ports:
        - containerPort: 8000
        command:
          - dgraph-ratel

拉起之后，会观察到
在这里插入图片描述
其中zero是管理节点
alpha是数据节点
ratel是提供的ui
在这里插入图片描述
有三个public的svc，就是对外提供的服务了，其中主要使用alpha和ratel的两个服务

配置ui

配置ingress nginx代理（http协议）
yaml配置文件ingress.yaml如下：

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: dgraph-ingress
  namespace: dgraph
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
spec:
  rules:
  - host: dgraph.lenovo.com
    http:
      paths:
      - path: /(.*)
        backend:
          serviceName: dgraph-ratel-public
          servicePort: 8000
      - path: /zero/(.*)
        backend:
          serviceName: dgraph-zero-public
          servicePort: 6080
      - path: /alpha/(.*)
        backend:
          serviceName: dgraph-alpha-public
          servicePort: 8080


kubectl apply -f ingress.yaml

配置hosts：

10.110.149.173 dgraph.lenovo.com
10.110.149.173 grpc.dgraph.lenovo.com

在浏览器上面访问：http://dgraph.lenovo.com/
在这里插入图片描述
选择中间的
然后可以看到：
在这里插入图片描述
配置Draph server URL:http://dgraph.lenovo.com/alpha
点击connect，连接成功，然后就可以愉快的使用dgraph了。

使用java client连接dgraph

参考https://blog.csdn.net/weixin_38166686/article/details/102452691

概述

一般情况下，我们的系统对外暴露HTTP/HTTPS的接口，内部使用rpc(GRPC)通讯，这时GRPC在服务之间通过service访问，本地调试时通过service nodePort方式调用。
但随着业务壮大，需要跨集群的GRPC通讯，或者pod数量太多、nodePort端口管理混乱时，就可以考虑用ingress来统一管理和暴露GRPC服务了。

本文详细介绍如何在kubernetes用ingress负载grpc服务。

  • 首先需要特别留意：ingress-nginx不支持负载明文的grpc（这个官方居然没明说，巨坑，详情请自行搜索github上的issues），所以只能在443端口上用TLS来负载。

生成公钥

前面说了ingress只支持在443端口上负载加密的grpc，所以在正式搭建前需要准备一组公私钥。
这里我们可以自行生成一组普通的公私钥，下面的命令将在当前目录生成一组公私钥文件：

[root@po-jenkins crt]# openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ca.key -out ca.crt -subj "/CN=grpc.dgraph.lenovo.com/O=grpc.dgraph.lenovo.com"
Generating a 2048 bit RSA private key
.....................+++
....+++
writing new private key to 'ca.key'
-----
[root@po-jenkins crt]# ls
ca.crt  ca.key

参数说明：

  1. ca.key: 私钥文件名
  2. ca.crt: 公钥文件名
  3. grpc.dgraph.lenovo.com: 域名后缀，后续所有使用此公私钥对的域名必须以grpc.dgraph.lenovo.com为后缀

生成k8s的secret

[root@po-jenkins crt]# kubectl create secret tls grpc-secret --key  ca.key --cert ca.crt -n dgraph
secret/grpc-secret created

编辑grpc-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: grpc-ingress
  namespace: dgraph
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/backend-protocol: "GRPC"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
spec:
  tls:
  - secretName: grpc-secret
    hosts:
      - grpc.dgraph.lenovo.com
  rules:
  - host: grpc.dgraph.lenovo.com
    http:
      paths:
      - path: /
        backend:
          serviceName: dgraph-alpha-public
          servicePort: 9080

生成grpc ingress

[root@po-jenkins crt]# kubectl apply -f grpc-ingress.yaml
ingress.extensions/grpc-ingress created

参数说明：

  1. 启用nginx：kubernetes.io/ingress.class: “nginx”
  2. 启用TLS，下面两项2选1：
    • 由nginx负责tls，服务内部还是用明文传输：nginx.ingress.kubernetes.io/ssl-redirect: “true”、nginx.ingress.kubernetes.io/backend-protocol: “GRPC”
    • 由服务自行实现TLS，nginx只负责路由：nginx.ingress.kubernetes.io/backend-protocol: “GRPCS”
  3. 域名：rules.host、tls.hosts这两个是该grpc服务的ingress域名，可以自定义，但必须以前面生成公私钥对时使用的后缀结尾
  4. 服务: grpc服务的服务名和端口由rules.http.backend配置
  5. 公私钥: tls.secretName指向前面创建的grpcs-secret
    注意：ingress-nginx的搭建，最好使用官方的yaml文件，自定义的配置可能会有冲突之处。

java终端访问

访问代码如下：

public String dgraph() throws SSLException {
        SslContextBuilder builder = GrpcSslContexts.forClient();
        builder.trustManager(new File("E:/engine/workspaces/crt/ca.crt"));
        SslContext sslContext = builder.build();
        ManagedChannel channel = NettyChannelBuilder.forAddress("grpc.dgraph.lenovo.com", 443)
                .sslContext(sslContext)
                .build();
        DgraphGrpc.DgraphStub stub = DgraphGrpc.newStub(channel);
        DgraphClient dgraphClient = new DgraphClient(stub);
        String json = "{    findNames(func: has(name)){            name     }    }";
        Map<String, String> vars = new HashMap<>();
        DgraphProto.Response response = dgraphClient.newReadOnlyTransaction().queryWithVars(json, vars);
        String result = response.getJson().toStringUtf8();
        System.out.println(result);
        return result;
    }

调用结果：

{
	"findNames": [{
		"name": "pre_processed_data"
	}, {
		"name": "annotated_data"
	}, {
		"name": "raw_data"
	}, {
		"name": "bu_data"
	}, {
		"name": "bot_data_platform"
	}, {
		"name": "web_crawler"
	}]
}

错误举例

访问的域名，必须与生成证书的域名一致，切记，否则会出现

8月 12, 2020 2:29:00 下午 org.apache.catalina.core.ApplicationContext log
信息: Initializing Spring DispatcherServlet 'dispatcherServlet'
2020-08-12 14:29:00,963:  Initializing Servlet 'dispatcherServlet'
2020-08-12 14:29:00,975:  Completed initialization in 11 ms
8月 12, 2020 2:29:03 下午 org.apache.catalina.core.StandardWrapperValve invoke
严重: Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.RuntimeException: The doRequest encountered an execution exception:] with root cause
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141)
	at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126)
	at java.base/java.security.cert.CertPathBuilder.build(CertPathBuilder.java:297)
	at java.base/sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:379)
	at java.base/sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:289)
	at java.base/sun.security.validator.Validator.validate(Validator.java:264)
	at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:285)
	at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:144)
	at io.netty.handler.ssl.ReferenceCountedOpenSslClientContext$ExtendedTrustManagerVerifyCallback.verify(ReferenceCountedOpenSslClientContext.java:255)
	at io.netty.handler.ssl.ReferenceCountedOpenSslContext$AbstractCertificateVerifier.verify(ReferenceCountedOpenSslContext.java:701)
	at io.netty.internal.tcnative.SSL.readFromSSL(Native Method)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.readPlaintextData(ReferenceCountedOpenSslEngine.java:593)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1176)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1293)
	at io.netty.handler.ssl.ReferenceCountedOpenSslEngine.unwrap(ReferenceCountedOpenSslEngine.java:1336)
	at io.netty.handler.ssl.SslHandler$SslEngineType$1.unwrap(SslHandler.java:204)
	at io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1332)
	at io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1227)
	at io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1274)
	at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:503)
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:442)
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:281)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:931)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:700)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:635)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:552)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514)
	at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:830)

或者

No subject alternative DNS name matching XXXX found

常用的命令：

openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout ca.key -out ca.crt -subj "/CN=dgraph.nlp.lenovo.com/O=dgraph.nlp.lenovo.com"
kubectl delete secret/grpc-secret -n dgraph
kubectl create secret tls grpc-secret --key  ca.key --cert ca.crt -n dgraph -o yaml  --dry-run=client  > ../secret.yaml
kubectl delete ingress/grpc-ingress -n dgraph
kubectl apply -f ../secret.yaml
kubectl apply -f ../grpc-ingress.yaml
月夜楓
关注
  • 0
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
ingress-nginx-controller-1.9.yaml
10-18
对于 "nginx-tomcat-svc-ingress.yaml" 和 "nginx-tomcat-deploy.yaml"，同样使用 `kubectl apply` 命令进行部署，以启动 Tomcat 应用并设置其 Ingress 规则。 验证配置是否生效的方法有很多，例如，你可以使用 `...
ingress实现grpc转发
qq_19344391的博客
05-04 1782
目录 准备测试环境 准备GRPC服务 准备测试GRPC服务的命令行工具 nginx-ingress-controller配置grpc转发 nginx-ingress-controller配置grpc-明文转发 nginx-ingress-controller配置grpc-TLS转发 traefik1.x配置grpc转发 traefik1.x配置grpc-明文转发 traefik1.x配置grpc-TLS转发 准备测试环境 准备GRPC服务 在kubernetes集群上部署GRPC服务
Ingress企业实战：实现GRPC与WebSocket服务访问
云原生运维
09-10 529
gRPC（gRPC Remote Procedure Call）是一种开源的远程过程调用（RPC）框架，由Google开发并于2015年发布。它使用HTTP/2协议进行通信，旨在简化跨网络的服务通信和跨语言的服务调用。IDL（Interface Definition Language）: gRPC 使用IDL来定义服务接口和消息格式。它使用Protocol Buffers（通常简称为ProtoBuf）作为默认的IDL工具。
k8s ingress(nginx) 反向代理集群外的服务
weixin_59526725的博客
04-22 376
Kubernetes 将根据服务的选择器（selector label）找到符合条件的 Pod，并将它们的 IP 和端口信息添加到 Endpoints 中。可以把 Service 理解为一个四层负载均衡器，而后端的 pod ip和端口信息是填写在 Endpoints 中的，Service 的转发也是根据 Endpoints。它允许你将 HTTP 和 HTTPS 流量路由到集群内的不同服务，同时提供了对负载均衡、SSL 终止、虚拟主机和路由等功能的支持。然后就可以在浏览器中用域名和默认端口访问代理的服务了。
nginx-ingress基于gRPC协议通信
zing的博客
01-08 983
此文档演示如何通过nginx-ingress将流量路由到gRPC服务上。 环境 环境 版本 kubernetes 1.17.4 Rancher v2.4.5 nginx-ingress 0.25.1 示例 以下gRPC应用基于ingress自带的示例，您也可以使用自己的gRPC应用进行测试 地址：https://github.com/kubernetes/ingress-nginx/tree/master/docs/examples/grpc 部署一个gRPC应用 该应用程序
如何通过 Nginx Ingress 快速解决 gRPC 长连接负载不均衡问题
easylife206的专栏
11-06 920
公众号关注「奇妙的 Linux 世界」设为「星标」，每天带你玩转 Linux ！背景当前推荐引擎服务集群的外部访问入口及负载均衡使用的是阿里云的SLB,然而其负载均衡,由于grpc长连接的缘故,表现不尽如人意,尽管加了定时重连的相关配置,多个pod依然会有旱的旱死,涝的涝死的情况.刚好新建的k8s集群版模型服务这种情况也比较明显,所以相关的优化就被提上了日程.听说新版的nginx-ingress...
ingress-nginx-controller（含镜像和代码）.rar
10-28
Nginx 作为业界广泛使用的高性能反向代理服务器，其稳定性和性能使得 ingress-nginx 成为了 Kubernetes 集群的首选 ingress 控制器。 二、Ingress 资源理解 Ingress 是 Kubernetes 中的一个 API 对象，用于定义...
ingress-nginx-4.0.17
02-18
ingress-nginx则是最广泛使用的ingress控制器之一，基于流行的Nginx反向代理服务器，提供了丰富的功能和高度的可配置性。 ingress-nginx-4.0.17作为Helm图表，是一个用于安装和管理ingress-nginx控制器的工具。Helm...
ingress nginx插件下载
11-12
ingress nginx插件yml文件，免费，免费，免费，免费免费
ingress-nginx.tar离线安装包，适用k8s版本 1.25.x~1.28.x
最新发布
05-22
ingress-nginx.tar离线安装包，适用k8s版本 1.25.x~1.28.x
使用k8s Ingress暴露gRPC服务
全栈工程师开发手册（原创）https://github.com/tencentmusic/cube-studio
04-18 1685
Kubernetes 暴露服务的方式目前只有三种：LoadBlancer Service、NodePort Service、Ingress；前两种估计都应该很熟悉，下面详细的了解下这个 Ingress Ingress由两部分组成：Ingress Controller 和 Ingress 服务。 参考:https://www.jianshu.com/p/189fab1845c5 ...
dgraph使用总结 ------ java api
m0_61812652的博客
11-29 653
dgraph---Java客户端
gRPC 之流式调用原理 http2 协议分析
蝉之洞
12-22 923
一、HTTP/1 协议回顾 HTTP (Hypertext transfer protocol) 超文本传输协议 HTTP 协议在 7 层传输架构中属于应用层协议，其依赖 TCP 协议 HTTP 协议由请求和响应两部分组成，是一个标准的客户端服务器模型 HTTP 默认端口号 80，https 默认端口号 443 HTTP 协议通过 URL（统一资源定位符 - Uniform-Resource-Locator）来定位互联网上的资源地址 HTTP 是一个无状态的面向连接的协议，无状态不代表 HTTP
NGINX Ingress Controller 配置代理外部服务
austindev的博客
07-29 3253
NGINX Ingress Controller 配置代理外部服务 背景说明 前端工程,在开发环境配置了本地代理 上线后需要服务端设置代理; 传统的nginx环境则直接配置如下即可 location /tencent-mapapi/ { proxy_redirect http:// $scheme://; #做https跳转; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; prox
nginx配置同时支持grpc(http2)方式传流以及http方式转发请求
xuxuxu1222的博客
05-13 7383
nginx配置同时支持grpc(http2)方式传流以及http方式转发请求 在网上找了很多配置都千篇一律不管用。废话不说，直接上配置 修改nginx.conf配置，在http{}里面添加如下内容： # 设置超时和发包大小 client_max_body_size 4000M; grpc_read_timeout 1d; grpc_send_timeout 1d; grpc_buffer_size...
使用nginx对grpc进行反向代理和负载均衡
liushuyul的博客
05-30 5323
前言 最近项目中需要给我们的grpc服务进行反向代理和负载均衡。故将这期间查阅的资料进行了整理记录 相关链接 介绍nginx负载均衡：https://blog.csdn.net/qq_51574197/article/details/117408823 nginx对grpc进行反向代理：https://blog.csdn.net/Dearmark/article/details/80066819 netty中http2的设计：https://my.oschina.net/u/1261452/blog/299
nginx使用长连接代理grpc流量
当赤道留住雪花
10-09 2262
Nginx在1.13.10版本支持了对grpc流量的反向代理，恰好业务有需求，要在sidecar容器中代理grpc流量。因此参考进行了配置。但是并未如预期般顺利运行，按照示例配置后，nginx与后端的grpc服务并非长连接，导致了一系列问题，在此做个记录。
【翻译】Kubernetes Ingress gRPC实例与Dune报价服务
超级码力
11-13 206
作者：Viktor Gamov2021年9月24日 特邀文章，最初发表在Kong的博客上，作者是Kong的首席开发者倡导者Viktor Gamov API有各种不同的形状和形式。在本教程中，我将向你展示一个Kubernetes Ingress gRPC实例。我将解释如何将gRPC服务部署到Kubernetes，并使用Kong的Kubernetes Ingress控制器提供对该服务的外部访问...
nginx-ingress配置(注解)
热门推荐
weixin_44692256的博客
12-02 1万+
ingress-nginx配置(注解) 注解 您可以将这些Kubernetes批注添加到特定的Ingress对象，以自定义其行为。 小费 注释键和值只能是字符串。其他类型，如布尔或数值必须被引用，即"true"，"false"，"100"。 注意 可以使用--annotations-prefix命令行参数更改注释前缀 ，但默认值为nginx.ingress.kubernetes.io，如下表所述。 Nametype nginx.ingress.kubernetes.io/app-rootstring
nginx 配置代理ingress
06-06
要在nginx中配置代理ingress，您需要完成以下步骤： 1. 安装nginx和相关模块（如果没有安装的话） 2. 创建一个nginx配置文件，例如“my-ingress.conf” 3. 在配置文件中定义一个upstream，用于将请求代理到后端...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值