v1 concept review updates

hashicorp · Oct 31, 2023 · bb96ad8 · bb96ad8
1 parent 0959179
commit bb96ad8
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/website/content/docs/architecture/catalog/v1.mdx b/website/content/docs/architecture/catalog/v1.mdx
@@ -12,20 +12,20 @@ For more information about the information returned when querying the catalog, i
 
 ## Introduction
 
-Consul tracks information about registered services through its Catalog API. This API records user-defined information about the external services, such as their partitions and required health checks. It also records information that Consul assigns for its own operations, such as an ID for each service instance and the [Raft indices](/consul/docs/architecture/consensus) when the instance is registered and modified.
+Consul tracks information about registered services through its catalog API. This API records user-defined information about the external services, such as their partitions and required health checks. It also records information that Consul assigns for its own operations, such as an ID for each service instance and the [Raft indices](/consul/docs/architecture/consensus) when the instance is registered and modified.
 
-Consul uses v1 of the catalog API by default. Consul v1.17.0 and later ships with version 2 (v2) of the catalog API. V2 is intended to be used for testing and development purposes. V1 and V2 of the catalog APIs cannot run concurrently in a Consul deployment. There is no migration path between catalog versions. For more information, refer to [Consul v2 Catalog API](/consul/docs/architecture/catalog/v2).
+Consul uses v1 of the catalog API by default. Consul v1.17.0 and later ships with version 2 (v2) of the catalog API. V2 is intended for testing and development purposes. V1 and V2 of the catalog APIs cannot run concurrently in a Consul deployment. There is no migration path between catalog versions. For more information, refer to [Consul v2 Catalog API](/consul/docs/architecture/catalog/v2).
 
 ## Catalog structure
 
 When Consul registers a service instance using the v1 catalog API, it records the following information about each instance:
 
 | v1 Catalog field | Description | Source |
 | :--------------- | :---------- | :----- |
-| ID | A unique identifier for a service instance. | Computed by Consul |
-| Node | The connection point where the service is available. | Computed by Consul |
-| Address  | The address of the node where the service instance is running. | Computed by Consul |
-| Tagged Addresses | User-defined metadata about addresses. | Defined by user |
+| ID | A unique identifier for a service instance. | Defined by user in [service definition](/consul/docs/services/configuration/services-configuration-reference#id). |
+| Node | The connection point where the service is available.  | On VMs, defined by user. <br /><br /> On Kubernetes, computed by Consul according to [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/). |
+| Address  | The registered address of the service instance. | Defined by user in [service definition](/consul/docs/services/configuration/services-configuration-reference#address). |
+| Tagged Addresses | User-defined labels for addresses. | Defined by user in [service definition](/consul/docs/services/configuration/services-configuration-reference#tags). |
 | NodeMeta | User-defined metadata about the node. | Defined by user |
 | Datacenter | The name of the datacenter the service is registered in. | Defined by user |
 | Service | The name of the service Consul registers the service instance under. | Defined by user |