mirror of https://github.com/dapr/docs.git
Merge pull request #4215 from hhunter-ms/issue_4207
Add namespacing landing page
This commit is contained in:
commit
0d65ac7e22
|
|
@ -0,0 +1,7 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Frequently asked questions and answers"
|
||||
linkTitle: "FAQs"
|
||||
weight: 1100
|
||||
description: "Learn more about Dapr concepts through frequently asked questions"
|
||||
---
|
||||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Frequently asked questions and answers"
|
||||
linkTitle: "FAQs"
|
||||
weight: 1000
|
||||
title: "General Dapr questions and answers"
|
||||
linkTitle: "General questions"
|
||||
weight: 100
|
||||
description: "Common questions asked about Dapr"
|
||||
---
|
||||
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
type: docs
|
||||
title: "Dapr and service meshes"
|
||||
linkTitle: "Service meshes"
|
||||
weight: 900
|
||||
weight: 200
|
||||
description: >
|
||||
How Dapr compares to and works with service meshes
|
||||
---
|
||||
|
|
@ -0,0 +1,45 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Isolation"
|
||||
linkTitle: "Isolation"
|
||||
weight: 700
|
||||
description: How Dapr provides namespacing and isolation
|
||||
---
|
||||
|
||||
Dapr namespacing provides isolation and multi-tenancy across many capabilities, giving greater security. Typically applications and components are deployed to namespaces to provide isolation in a given environment, such as Kubernetes.
|
||||
|
||||
Dapr supports namespacing in service invocation calls between applications, when accessing components, sending pub/sub messages in consumer groups, and with actors type deployments as examples. Namespacing isolation is supported in both self-hosted and Kubernetes modes.
|
||||
|
||||
To get started, create and configure your namespace.
|
||||
|
||||
{{< tabs "Self-Hosted" "Kubernetes">}}
|
||||
|
||||
{{% codetab %}}
|
||||
|
||||
In self-hosted mode, specify the namespace for a Dapr instance by setting the `NAMESPACE` environment variable.
|
||||
|
||||
{{% /codetab %}}
|
||||
|
||||
{{% codetab %}}
|
||||
|
||||
On Kubernetes, create and configure the namespace:
|
||||
|
||||
```bash
|
||||
kubectl create namespace namespaceA
|
||||
kubectl config set-context --current --namespace=namespaceA
|
||||
```
|
||||
|
||||
Then deploy your applications into this namespace.
|
||||
|
||||
{{% /codetab %}}
|
||||
|
||||
{{< /tabs >}}
|
||||
|
||||
Learn how to use namespacing throughout Dapr:
|
||||
|
||||
- [Service Invocation namespaces]({{< ref service-invocation-namespaces.md >}})
|
||||
- [How to: Set up pub/sub namespace consumer groups]({{< ref howto-namespace.md >}})
|
||||
- Components:
|
||||
- [How to: Configure pub/sub components with multiple namespaces]({{< ref pubsub-namespaces.md >}})
|
||||
- [Scope components to one or more applications]({{< ref component-scopes.md >}})
|
||||
- [Namespaced actors]({{< ref namespaced-actors.md >}})
|
||||
|
|
@ -2,7 +2,7 @@
|
|||
type: docs
|
||||
title: "Dapr terminology and definitions"
|
||||
linkTitle: "Terminology"
|
||||
weight: 900
|
||||
weight: 1000
|
||||
description: Definitions for common terms and acronyms in the Dapr documentation
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue