PortNameIsNotUnderNamingConvention

    2. kind: Service
    3. metadata:
    4.   name: httpbin
    5.     app: httpbin
    7.   ports:
    8.   - name: foo-http
    9.     port: 8000
    10.     targetPort: 80

    How to resolve

    • If you know the protocol the service port is serving, renaming the port with <protocol>[-<suffix>] format;
    • If you don’t know the protocol the service port is serving, you need to query metrics from Prometheus
      • Running query istio_requests_total{reporter="destination",destination_service_name="SERVICE_NAME",response_code="200"}[TIME_RANGE]. If you are using Mixer v2, you can also run query istio_requests_total{reporter="destination",destination_service_name="SERVICE_NAME",response_code="200",destination_port="TARGET_PORT"}[TIME_RANGE].
      • If there are outputs, you can find the from the record. E.g., if the request_protocol is “http”, renaming port to “http-foo”;
      • If there is no output, you can leave the port as it is.