Manual Backport of Docs: Clarify service.port allowed value types into release/1.9.x (#26347)

* no-op commit due to failed cherry-picking

* add table to service.port entry (#26344)

* fix cherry-pick

---------

Co-authored-by: temp <[email protected]>
Co-authored-by: Aimee Ukasick <[email protected]>

Author: 3 people

website/content/docs/job-specification/connect.mdx

@@ -49,8 +49,9 @@ job "countdash" {
 Used to configure a connect service. Only one of `native`, `sidecar_service`,
 or `gateway` may be realized per `connect` block.
 
-- `native` - `(bool: false)` - This is used to configure the service as supporting
-  [Connect Native](/consul/docs/connect/native) applications.
+- `native` - `(bool: false)` - This is used to configure the service as
+  supporting [Consul service mesh native][consul-service-mesh-native]
+  applications.
 
 - `sidecar_service` - <code>([sidecar_service][]: nil)</code> - This is used to
   configure the sidecar service created by Nomad for Consul Connect.
@@ -66,8 +67,11 @@ or `gateway` may be realized per `connect` block.
 ### Using Connect Native
 
 The following example is a minimal service block for a
-[Consul Connect Native](/consul/docs/connect/native)
-application implemented by a task named `generate`.
+[Consul service mesh native][consul-service-mesh-native]
+application implemented by a task named `generate`. Make sure to include the
+[service `name`](/nomad/docs/job-specification/service#name) and [service
+`port`](/nomad/docs/job-specification/service##port) fields so that Consul
+advertizes the service with your desired values.
 
 ```hcl
 service {
@@ -240,23 +244,13 @@ job "ingress-demo" {
 ### Limitations
 
 [gateway]: /nomad/docs/job-specification/gateway
-
 [gh-7221]: https://github.com/hashicorp/nomad/issues/7221
-
-[group]: /nomad/docs/job-specification/group "Nomad group Job Specification"
-
-[interpolation]: /nomad/docs/runtime/interpolation "Nomad interpolation"
-
-[job]: /nomad/docs/job-specification/job "Nomad job Job Specification"
-
-[native]: /consul/docs/connect/native
-
-[service_task]: /nomad/docs/job-specification/service#task-1 "Nomad service task"
-
-[sidecar_service]: /nomad/docs/job-specification/sidecar_service "Nomad sidecar service Specification"
-
-[sidecar_task]: /nomad/docs/job-specification/sidecar_task "Nomad sidecar task config Specification"
-
-[task]: /nomad/docs/job-specification/task "Nomad task Job Specification"
-
-[upstreams]: /nomad/docs/job-specification/upstreams "Nomad sidecar service upstreams Specification"
+[group]: /nomad/docs/job-specification/group
+[interpolation]: /nomad/docs/reference/runtime-variable-interpolation
+[job]: /nomad/docs/job-specification/job
+[service_task]: /nomad/docs/job-specification/service#task-1
+[sidecar_service]: /nomad/docs/job-specification/sidecar_service
+[sidecar_task]: /nomad/docs/job-specification/sidecar_task
+[task]: /nomad/docs/job-specification/task
+[upstreams]: /nomad/docs/job-specification/upstreams
+[consul-service-mesh-native]: /consul/docs/automate/native

website/content/docs/job-specification/service.mdx

@@ -16,8 +16,8 @@ description: |-
 />
 
 The `service` block instructs Nomad to register a service with the specified
-provider; Nomad or Consul. This section of the documentation will discuss the
-configuration, but please also read the
+provider: Nomad or Consul. This section of the documentation discusses the
+configuration, but you should also read the
 [Nomad service discovery documentation][service-discovery] for more detailed
 information about the external integrations.
 
@@ -71,13 +71,13 @@ job "docs" {
 }
 ```
 
-This section of the documentation only cover the job file fields and blocks
-for service discovery. For more details on using Nomad with Consul please see
+This section of the documentation only covers the job file fields and blocks
+for service discovery. For more details on using Nomad with Consul, refer to
 the [Consul integration documentation][service-discovery].
 
 The `service` block can also be at task group level.
 This enables services in the same task group to opt into [Consul
-Service Mesh][connect] integration.
+service mesh][connect] integration.
 
 ## `service` Parameters
 
@@ -152,6 +152,15 @@ Service Mesh][connect] integration.
   - `host` - Advertise the host port for this service. `port` must match a port
     _label_ specified in the [`network`][network] block.
 
+  | Service kind | Allowed port value type |
+  | -------- | ------- |
+  | Normal       | Numeric or port mapping label |
+  | Uses [`connect` native][connect-native] | Numeric or port mapping label |
+  | Uses [`connect` sidecar][connect-sidecar] | Numeric |
+  | Ingress gateway | Port mapping label (optional) |
+  | Terminating gateway | None (optional) |
+  | Mesh gateway | External port mapping label |
+
 - `tags` `(array<string>: [])` - Specifies the list of tags to associate with
   this service. If this is not supplied, no tags will be assigned to the service
   when it is registered.
@@ -202,7 +211,7 @@ Service Mesh][connect] integration.
 
 - `task` `(string: "")` - Specifies the name of the Nomad task associated with
   this service definition. Only available on group services. Must be set if this
-  service definition represents a Consul Connect-native service and there is more
+  service definition represents a Consul service mesh native service and there is more
   than one task in the task group.
 
 - `meta` <code>([Meta][]: nil)</code> - Specifies a key-value map that annotates
@@ -549,3 +558,5 @@ advertise and check directly since Nomad isn't managing any port assignments.
 [`consul.service_identity`]: /nomad/docs/configuration/consul#service_identity
 [identity_block]: /nomad/docs/job-specification/identity
 [weights]: /consul/docs/services/configuration/services-configuration-reference#weights
+[connect-sidecar]: /nomad/docs/job-specification/connect#using-sidecar-service
+[connect-native]: /nomad/docs/job-specification/connect#using-consul-service-mesh-native