Merge 32bdd2c into backport/docs/remove-partition-from-crds-docs/hear…

…tily-fleet-insect

website/content/docs/connect/config-entries/ingress-gateway.mdx

@@ -94,7 +94,7 @@ spec:
 
 <Tab heading="Consul Enterprise">
 
-For Kubernetes environments, the CRD inherits the partition from the cluster hosting the pods.
+For Kubernetes environments, the configuration entry is always created in the same partition as the Kubernetes cluster.
 
 <CodeTabs tabs={[ "HCL", "Kubernetes YAML", "JSON" ]}>
 

website/content/docs/services/usage/define-services.mdx

@@ -145,7 +145,7 @@ If Consul service mesh is enabled in your network, you can define default values
 
 Create a file for the configuration entry and specify the required fields. If you are authoring `service-defaults` in HCL or JSON, the `Kind` and `Name` fields are required. On Kubernetes, the `apiVersion`, `kind`, and `metadata.name` fields are required. Refer to [Service Defaults Reference](/consul/docs/connect/config-entries/service-defaults) for details about the configuration options.
 
-If you use Consul Enterprise, you can also specify the `Namespace` and `Partition` fields to apply the configuration to services in specific network areas. In Kubernetes environments, For Kubernetes environments, the CRD inherits the partition from the cluster hosting the pods. 
+If you use Consul Enterprise, you can also specify the `Namespace` and `Partition` fields to apply the configuration to services in a specific namespace or partition. For Kubernetes environments, the configuration entry is always created in the same partition as the Kubernetes cluster.
 
 ### Consul OSS example
 The following example instructs services named `counting` to send up to `512` concurrent requests to a mesh gateway: