apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: frontend-applications-ingress namespace: sc-my-uav-260202 labels: type: frontend octopus.control: all-ingress-config-wdd app.kubernetes.io/managed-by: octopus-control app.kubernetes.io/version: uas-2.2 annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/enable-cors: 'true' nginx.ingress.kubernetes.io/rewrite-target: /$1 spec: rules: - host: fake-domain.sc-my-uav-260202.io http: paths: - path: /?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform port: number: 9528 - path: /supervision/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-suav-platform-supervision port: number: 9528 - path: /supervisionh5/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-suav-platform-supervisionh5 port: number: 9528 - path: /pangu/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform port: number: 9528 - path: /ai-brain/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-ai-brain port: number: 9528 - path: /armypeople/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-armypeople port: number: 9528 - path: /awareness/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-awareness port: number: 9528 - path: /base/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-base port: number: 9528 - path: /blockchain/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-blockchain port: number: 9528 - path: /classification/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-classification port: number: 9528 - path: /cmsportal/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-cms-portal port: number: 9528 - path: /detection/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-detection port: number: 9528 - path: /dikongzhixingh5/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-dikongzhixingh5 port: number: 9528 - path: /dispatchh5/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-dispatchh5 port: number: 9528 - path: /emergency/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-emergency-rescue port: number: 9528 - path: /eventsh5/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-eventsh5 port: number: 9528 - path: /flight-control/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-flight-control port: number: 9528 - path: /hljtt/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-hljtt port: number: 9528 - path: /hyper/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-hyperspectral port: number: 9528 - path: /iot/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-iot-manager port: number: 9528 - path: /jiangsuwenlv/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-jiangsuwenlv port: number: 9528 - path: /logistics/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-logistics port: number: 9528 - path: /media/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-media port: number: 9528 - path: /mianyangbackend/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-mianyangbackend port: number: 9528 - path: /multiterminal/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-multiterminal port: number: 9528 - path: /mws/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-mws port: number: 9528 - path: /oms/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-oms port: number: 9528 - path: /open/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-open port: number: 9528 - path: /pilot2cloud/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-pilot2-to-cloud port: number: 9528 - path: /qingdao/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-qingdao port: number: 9528 - path: /qinghaitourism/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-qinghaitourism port: number: 9528 - path: /renyike/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-renyike port: number: 9528 - path: /scanner/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-scanner port: number: 9528 - path: /security/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-security port: number: 9528 - path: /securityh5/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-securityh5 port: number: 9528 - path: /seniclive/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-seniclive port: number: 9528 - path: /share/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-share port: number: 9528 - path: /smauth/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-smauth port: number: 9528 - path: /smsecret/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-smsecret port: number: 9528 - path: /splice/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-splice port: number: 9528 - path: /threedsimulation/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-threedsimulation port: number: 9528 - path: /traffic/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-traffic port: number: 9528 - path: /uas/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-uas port: number: 9528 - path: /uas/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-uaskny port: number: 9528 - path: /uasms/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-uasms port: number: 9528 - path: /uasms/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-uasmskny port: number: 9528 - path: /visualization/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-platform-visualization port: number: 9528 - path: /uavmsmanager/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uavms-platform-manager port: number: 9528 - path: /secenter/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uavms-platform-security-center port: number: 9528 --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: backend-applications-ingress namespace: sc-my-uav-260202 labels: type: backend octopus.control: all-ingress-config-wdd app.kubernetes.io/managed-by: octopus-control app.kubernetes.io/version: uas-2.2 annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/enable-cors: 'true' spec: rules: - host: cmii-admin-data.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-admin-data port: number: 8080 - host: cmii-admin-gateway.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-admin-gateway port: number: 8080 - host: cmii-admin-user.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-admin-user port: number: 8080 - host: cmii-app-release.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-app-release port: number: 8080 - host: cmii-open-gateway.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-open-gateway port: number: 8080 - host: cmii-sky-converge.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-sky-converge port: number: 8080 - host: cmii-suav-supervision.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-suav-supervision port: number: 8080 - host: cmii-uas-datahub.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uas-datahub port: number: 8080 - host: cmii-uas-gateway.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uas-gateway port: number: 8080 - host: cmii-uas-lifecycle.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uas-lifecycle port: number: 8080 - host: cmii-uav-advanced5g.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-advanced5g port: number: 8080 - host: cmii-uav-airspace.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-airspace port: number: 8080 - host: cmii-uav-alarm.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-alarm port: number: 8080 - host: cmii-uav-autowaypoint.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-autowaypoint port: number: 8080 - host: cmii-uav-brain.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-brain port: number: 8080 - host: cmii-uav-bridge.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-bridge port: number: 8080 - host: cmii-uav-cloud-live.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-cloud-live port: number: 8080 - host: cmii-uav-clusters.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-clusters port: number: 8080 - host: cmii-uav-cms.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-cms port: number: 8080 - host: cmii-uav-data-post-process.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-data-post-process port: number: 8080 - host: cmii-uav-depotautoreturn.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-depotautoreturn port: number: 8080 - host: cmii-uav-developer.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-developer port: number: 8080 - host: cmii-uav-device.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-device port: number: 8080 - host: cmii-uav-emergency.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-emergency port: number: 8080 - host: cmii-uav-fwdd.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-fwdd port: number: 8080 - host: cmii-uav-gateway.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-gateway port: number: 8080 - host: cmii-uav-gis-server.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-gis-server port: number: 8080 - host: cmii-uav-grid-datasource.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-grid-datasource port: number: 8080 - host: cmii-uav-grid-engine.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-grid-engine port: number: 8080 - host: cmii-uav-grid-manage.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-grid-manage port: number: 8080 - host: cmii-uav-industrial-portfolio.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-industrial-portfolio port: number: 8080 - host: cmii-uav-integration.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-integration port: number: 8080 - host: cmii-uav-iot-dispatcher.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-iot-dispatcher port: number: 8080 - host: cmii-uav-iot-manager.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-iot-manager port: number: 8080 - host: cmii-uav-kpi-monitor.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-kpi-monitor port: number: 8080 - host: cmii-uav-logger.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-logger port: number: 8080 - host: cmii-uav-material-warehouse.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-material-warehouse port: number: 8080 - host: cmii-uav-mission.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-mission port: number: 8080 - host: cmii-uav-mqtthandler.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-mqtthandler port: number: 8080 - host: cmii-uav-multilink.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-multilink port: number: 8080 - host: cmii-uav-notice.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-notice port: number: 8080 - host: cmii-uav-oauth.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-oauth port: number: 8080 - host: cmii-uav-process.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-process port: number: 8080 - host: cmii-uav-sec-awareness.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-sec-awareness port: number: 8080 - host: cmii-uav-security-trace.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-security-trace port: number: 8080 - host: cmii-uav-sense-adapter.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-sense-adapter port: number: 8080 - host: cmii-uav-surveillance.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-surveillance port: number: 8080 - host: cmii-uav-sync.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-sync port: number: 8080 - host: cmii-uav-tcp-server.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-tcp-server port: number: 8080 - host: cmii-uav-threedsimulation.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-threedsimulation port: number: 8080 - host: cmii-uav-tower.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-tower port: number: 8080 - host: cmii-uav-user.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-user port: number: 8080 - host: cmii-uav-watchdog.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-watchdog port: number: 8080 - host: cmii-uav-waypoint.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uav-waypoint port: number: 8080 - host: cmii-uavms-pyfusion.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uavms-pyfusion port: number: 8080 - host: cmii-uavms-security-center.uavcloud-sc-my-202602.io http: paths: - path: / pathType: ImplementationSpecific backend: service: name: cmii-uavms-security-center port: number: 8080 --- apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: all-gateways-ingress namespace: sc-my-uav-260202 labels: type: api-gateway octopus.control: all-ingress-config-1.1.0 app.kubernetes.io/managed-by: octopus-control app.kubernetes.io/version: uas-2.2 annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/enable-cors: 'true' nginx.ingress.kubernetes.io/rewrite-target: /$1 nginx.ingress.kubernetes.io/proxy-read-timeout: '3600' nginx.ingress.kubernetes.io/proxy-send-timeout: '3600' spec: rules: - host: fake-domain.sc-my-uav-260202.io http: paths: - path: /oms/api/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-admin-gateway port: number: 8080 - path: /open/api/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-open-gateway port: number: 8080 - path: /api/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uav-gateway port: number: 8080 - path: /uas/api/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-uas-gateway port: number: 8080 - path: /converge/?(.*) pathType: ImplementationSpecific backend: service: name: cmii-sky-converge port: number: 8080