Port
Port structure to capture port information for the pod.
Name field of tag name
Port Name to be used in the pod configuration. Conveys no actual meaning, but should obey Kubernetes naming standards. Some tools might rely on this metadata to identify the ports automatically and define policies accordingly.
Port field of tag port
Port number to be used for the protocol in the pod configuration. The value should be between 1 and 65535 based on the TCP/IP standard.
Transport field of tag transport
Transport protocol of the referred port in lower-case spelling. Only "tcp", "udp", and "sctp" are supported. Other transport protocols may need specific kernel modules to be loaded in the nodes, which is not the case. To avoid confusion and due to the protocol ossification, custom transport protocols should be implemented as extension of the existing ones, respecting the specifications.
Application field of tag application
Application protocol used in this port. Could be made up as long as follows the format and later would be prepended with Trirematics subdomains. Prepending the Trirematics subdomain is required to avoid conflicts with other applications. If you have a service mesh deployed, make sure to configure the service mesh properly to use Trirematics subdomain.