Namespace
Namespace represents a namespace across the Fleet. To get more information about Namespace, see:
How-to Guides
Registering a Cluster {{% examples %}}
Example Usage
{{% /examples %}}
Import
Namespace can be imported using any of these accepted formats* projects/{{project}}/locations/global/scopes/{{scope_id}}/namespaces/{{scope_namespace_id}} * {{project}}/{{scope_id}}/{{scope_namespace_id}} * {{scope_id}}/{{scope_namespace_id}} In Terraform v1.5.0 and later, use an import block to import Namespace using one of the formats above. For exampletf import { id = "projects/{{project}}/locations/global/scopes/{{scope_id}}/namespaces/{{scope_namespace_id}}" to = google_gke_hub_namespace.default }
$ pulumi import gcp:gkehub/namespace:Namespace When using the [`terraform import` command](https://developer.hashicorp.com/terraform/cli/commands/import), Namespace can be imported using one of the formats above. For example$ pulumi import gcp:gkehub/namespace:Namespace default projects/{{project}}/locations/global/scopes/{{scope_id}}/namespaces/{{scope_namespace_id}}$ pulumi import gcp:gkehub/namespace:Namespace default {{project}}/{{scope_id}}/{{scope_namespace_id}}$ pulumi import gcp:gkehub/namespace:Namespace default {{scope_id}}/{{scope_namespace_id}}Properties
Namespace-level cluster namespace labels. These labels are applied to the related namespace of the member clusters bound to the parent Scope. Scope-level labels (namespace_labels in the Fleet Scope resource) take precedence over Namespace-level labels if they share a key. Keys and values must be Kubernetes-conformant.