PortNameIsNotUnderNamingConvention

Message NamePortNameIsNotUnderNamingConvention
Message CodeIST0118
DescriptionPort name is not under naming convention. Protocol detection is applied to the port.
LevelInfo

This message occurs when the port doesn’t follow the Istio service port naming convention or the port is unnamed.

Example

You will receive this message:

  1. Info [IST0118] (Service httpbin.default) Port name foo-http (port: 80, targetPort: 80) doesn't follow the naming convention of Istio port.

when your cluster has following service:

  1. apiVersion: v1
  2. kind: Service
  3. metadata:
  4. name: httpbin
  5. labels:
  6. app: httpbin
  7. spec:
  8. ports:
  9. - name: foo-http
  10. port: 8000
  11. targetPort: 80
  12. selector:
  13. app: httpbin

In this example, the port name foo-http does not follow the syntax: name: <protocol>[-<suffix>].

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 request_protocol 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.