Nginx Ingress配置参考yaml文件

1.前端服务

apiVersion: networking.k8s.io/v1beta1

kind: Ingress

metadata:

  annotations:

    ingress.cloud.tencent.com/direct-access: "false"

    kubernetes.io/ingress.class: nginx

    kubernetes.io/ingress.extensiveParameters: '{"AddressIPVersion":"IPV4"}'

    kubernetes.io/ingress.http-rules: '[{"host":"*.*","path":"/","backend":{"serviceName":"aps-web","servicePort":"80"}}]'

    kubernetes.io/ingress.https-rules: "null"

    kubernetes.io/ingress.rule-mix: "true"

  creationTimestamp: "2021-06-17T09:19:53Z"

  generation: 3

  managedFields:

  - apiVersion: networking.k8s.io/v1beta1

    manager: nginx-ingress-controller

    operation: Update

    time: "2021-06-17T09:20:05Z"

  - apiVersion: networking.k8s.io/v1beta1

    manager: tke-apiserver

    operation: Update

    time: "2021-06-18T00:52:15Z"

  name: ingressaps

  namespace: mes

  resourceVersion: "5856587364"

  selfLink: /apis/networking.k8s.io/v1beta1/namespaces/mes/ingresses/ingressaps

  uid: e46689d8-dcc9-4c2e-8c10-651cc0b0dbf0

spec:

  rules:

  - host: *.*

    http:

      paths:

      - backend:

          serviceName: aps-web

          servicePort: 80

        path: /

status:

  loadBalancer:

    ingress:

    - ip: *.*

2.后端服务

apiVersion: networking.k8s.io/v1beta1

kind: Ingress

metadata:

  annotations:

    ingress.cloud.tencent.com/direct-access: "false"

    kubernetes.io/ingress.class: nginx

    kubernetes.io/ingress.extensiveParameters: '{"AddressIPVersion":"IPV4"}'

    kubernetes.io/ingress.http-rules: '[{"host":"*.*","path":"/nkapi","backend":{"serviceName":"aps-nkaps-api","servicePort":"5000"}}]'

    kubernetes.io/ingress.https-rules: "null"

    kubernetes.io/ingress.rule-mix: "true"

    nginx.ingress.kubernetes.io/app-root: /

  creationTimestamp: "2021-06-18T01:11:15Z"

  generation: 1

  managedFields:

  - apiVersion: networking.k8s.io/v1beta1

    manager: nginx-ingress-controller

    operation: Update

    time: "2021-06-18T01:12:05Z"

  - apiVersion: networking.k8s.io/v1beta1

    manager: tke-apiserver

    operation: Update

    time: "2021-06-18T02:58:28Z"

  name: ingressapsnkapi

  namespace: mes

  resourceVersion: "5860841564"

  selfLink: /apis/networking.k8s.io/v1beta1/namespaces/mes/ingresses/ingressapsnkapi

  uid: 48a110ed-7911-4e86-8bd4-c7f66035d78e

spec:

  rules:

  - host: *.*

    http:

      paths:

      - backend:

          serviceName: aps-nkaps-api

          servicePort: 5000

        path: /nkapi(/|$)(.*)

status:

  loadBalancer:

    ingress:

    - ip: *.*

3.后端服务

apiVersion: networking.k8s.io/v1beta1

kind: Ingress

metadata:

  annotations:

    ingress.cloud.tencent.com/direct-access: "false"

    kubernetes.io/ingress.class: nginx

    kubernetes.io/ingress.extensiveParameters: '{"AddressIPVersion":"IPV4"}'

    kubernetes.io/ingress.http-rules: '[{"host":"*.*","path":"/api/adminnode","backend":{"serviceName":"zt-admin-node","servicePort":"8016"}}]'

    kubernetes.io/ingress.https-rules: "null"

    kubernetes.io/ingress.rule-mix: "true"

    nginx.ingress.kubernetes.io/rewrite-target: /$2

  creationTimestamp: "2020-12-29T03:12:20Z"

  generation: 10

  managedFields:

  - apiVersion: networking.k8s.io/v1beta1

    manager: nginx-ingress-controller

    operation: Update

    time: "2021-04-30T03:42:06Z"

  - apiVersion: networking.k8s.io/v1beta1

    manager: tke-apiserver

    operation: Update

    time: "2021-06-15T01:28:00Z"

  name: ztingress-admin

  namespace: mes

  resourceVersion: "5714922901"

  selfLink: /apis/networking.k8s.io/v1beta1/namespaces/mes/ingresses/ztingress-admin

  uid: 6da2e706-622d-47f3-850b-7d21619d55cb

spec:

  rules:

  - host: ztapi.*.*

    http:

      paths:

      - backend:

          serviceName: zt-admin-node

          servicePort: 8016

        path: /api/adminnode(/|$)(.*)

status:

  loadBalancer:

    ingress:

    - ip: *.*.1.2

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
在信号处理领域,DOA(Direction of Arrival)估计是一项关键技术,主要用于确定多个信号源到达接收阵列的方向。本文将详细探讨三种ESPRIT(Estimation of Signal Parameters via Rotational Invariance Techniques)算法在DOA估计中的实现,以及它们在MATLAB环境中的具体应用。 ESPRIT算法是由Paul Kailath等人于1986年提出的,其核心思想是利用阵列数据的旋转不变性来估计信号源的角度。这种算法相比传统的 MUSIC(Multiple Signal Classification)算法具有较低的计算复杂度,且无需进行特征值分解,因此在实际应用中颇具优势。 1. 普通ESPRIT算法 普通ESPRIT算法分为两个主要步骤:构造等效旋转不变系统和估计角度。通过空间平移(如延时)构建两个子阵列,使得它们之间的关系具有旋转不变性。然后,通过对子阵列数据进行最小二乘拟合,可以得到信号源的角频率估计,进一步转换为DOA估计。 2. 常规ESPRIT算法实现 在描述中提到的`common_esprit_method1.m`和`common_esprit_method2.m`是两种不同的普通ESPRIT算法实现。它们可能在实现细节上略有差异,比如选择子阵列的方式、参数估计的策略等。MATLAB代码通常会包含预处理步骤(如数据归一化)、子阵列构造、旋转不变性矩阵的建立、最小二乘估计等部分。通过运行这两个文件,可以比较它们在估计精度和计算效率上的异同。 3. TLS_ESPRIT算法 TLS(Total Least Squares)ESPRIT是对普通ESPRIT的优化,它考虑了数据噪声的影响,提高了估计的稳健性。在TLS_ESPRIT算法中,不假设数据噪声是高斯白噪声,而是采用总最小二乘准则来拟合数据。这使得算法在噪声环境下表现更优。`TLS_esprit.m`文件应该包含了TLS_ESPRIT算法的完整实现,包括TLS估计的步骤和旋转不变性矩阵的改进处理。 在实际应用中,选择合适的ESPRIT变体取决于系统条件,例如噪声水平、信号质量以及计算资源。通过MATLAB实现,研究者和工程师可以方便地比较不同算法的效果,并根据需要进行调整和优化。同时,这些代码也为教学和学习DOA估计提供了一个直观的平台,有助于深入理解ESPRIT算法的工作原理。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值