diff --git a/README.md b/README.md index 768ba03c4..4997d48e5 100644 --- a/README.md +++ b/README.md @@ -12,10 +12,10 @@ The Dapr docs handles branching differently than most code repositories. Instead The following branches are currently maintained: -| Branch | Website | Description | -|--------|---------|-------------| -| [v1.4](https://github.com/dapr/docs) (primary) | https://docs.dapr.io | Latest Dapr release documentation. Typo fixes, clarifications, and most documentation goes here. -| [v1.5](https://github.com/dapr/docs/tree/v1.5) (pre-release) | https://v1-5.docs.dapr.io/ | Pre-release documentation. Doc updates that are only applicable to v1.5+ go here. +| Branch | Website | Description | +| ------------------------------------------------------------ | -------------------------- | ------------------------------------------------------------------------------------------------ | +| [v1.4](https://github.com/dapr/docs) (primary) | https://docs.dapr.io | Latest Dapr release documentation. Typo fixes, clarifications, and most documentation goes here. | +| [v1.5](https://github.com/dapr/docs/tree/v1.5) (pre-release) | https://v1-5.docs.dapr.io/ | Pre-release documentation. Doc updates that are only applicable to v1.5+ go here. | For more information visit the [Dapr branch structure](https://docs.dapr.io/contributing/contributing-docs/#branch-guidance) document. @@ -38,31 +38,43 @@ The [daprdocs](./daprdocs) directory contains the hugo project, markdown files, 1. Ensure pre-requisites are installed 2. Clone this repository + ```sh git clone https://github.com/dapr/docs.git ``` + 3. Change to daprdocs directory: + ```sh -cd ./docs/daprdocs +cd ./daprdocs ``` + 4. Update submodules: + ```sh git submodule update --init --recursive ``` + 5. Install npm packages: + ```sh npm install ``` ## Run local server + 1. Make sure you're still in the `daprdocs` directory 2. Run + ```sh hugo server ``` + 3. Navigate to `http://localhost:1313/` + ## Update docs + 1. Fork repo into your account 1. Create new branch 1. Commit and push changes to forked branch @@ -70,4 +82,5 @@ hugo server 1. Staging site will automatically get created and linked to PR to review and test ## Code of Conduct + Please refer to our [Dapr community code of conduct](https://github.com/dapr/community/blob/master/CODE-OF-CONDUCT.md). diff --git a/daprdocs/content/en/_index.md b/daprdocs/content/en/_index.md index 5243416f2..6ca2cff4c 100644 --- a/daprdocs/content/en/_index.md +++ b/daprdocs/content/en/_index.md @@ -3,6 +3,22 @@ type: docs no_list: true --- +
Welcome to the Dapr documentation site!
diff --git a/daprdocs/content/en/developing-applications/integrations/workflows.md b/daprdocs/content/en/developing-applications/integrations/workflows.md
index ec30a0e1e..7261e5ddf 100644
--- a/daprdocs/content/en/developing-applications/integrations/workflows.md
+++ b/daprdocs/content/en/developing-applications/integrations/workflows.md
@@ -128,7 +128,7 @@ Prerequisites:
1. Create a Config Map for the workflow:
```bash
- kubectl create configmap workflows --from-file ./samples/workflow1. json
+ kubectl create configmap workflows --from-file ./samples/workflow1.json
```
1. Create a secret containing the Azure Storage Account credentials. Replace the account name and key values below with the actual credentials:
@@ -228,4 +228,4 @@ Watch an example from the Dapr community call:
## Additional resources
- [Blog announcement](https://cloudblogs.microsoft.com/opensource/2020/05/26/announcing-cloud-native-workflows-dapr-logic-apps/)
-- [Repo](https://github.com/dapr/workflows)
\ No newline at end of file
+- [Repo](https://github.com/dapr/workflows)
diff --git a/daprdocs/content/en/getting-started/_index.md b/daprdocs/content/en/getting-started/_index.md
index 238fed7b3..6339d4a5e 100644
--- a/daprdocs/content/en/getting-started/_index.md
+++ b/daprdocs/content/en/getting-started/_index.md
@@ -11,7 +11,6 @@ Welcome to the Dapr getting started guide!
{{% alert title="Dapr Concepts" color="primary" %}}
If you are looking for an introductory overview of Dapr and learn more about basic Dapr terminology, it is recommended to visit the [concepts section]({{}}).
-{{< button text="Learn more" page="concepts" >}}
{{% /alert %}}
This guide will walk you through a series of steps to install, initialize and start using Dapr. The recommended way to get started with Dapr is to setup a local development environment (also referred to as [_self-hosted_ mode]({{< ref self-hosted >}})) which includes the Dapr CLI, Dapr sidecar binaries, and some default components that can help you start using Dapr quickly.
diff --git a/daprdocs/content/en/operations/components/certification-lifecycle.md b/daprdocs/content/en/operations/components/certification-lifecycle.md
index a1f18b264..8dca1bdc5 100644
--- a/daprdocs/content/en/operations/components/certification-lifecycle.md
+++ b/daprdocs/content/en/operations/components/certification-lifecycle.md
@@ -22,7 +22,7 @@ To make sure a component conforms to the standards set by Dapr, there are a set
The levels are as follows:
- [Alpha](#alpha)
- [Beta](#beta)
-- [General availability (GA)](#general-availability-ga)
+- [Stable](#stable)
### Alpha
@@ -42,11 +42,16 @@ All components start at the Alpha stage.
- The component contains a record of the conformance test result reviewed and approved by Dapr maintainers with specific components-contrib version
- Recommended for only non-business-critical uses because of potential for incompatible changes in subsequent releases
-### General Availability (GA)
+### Stable
-- Has at least two different users using the component in production
-- A GA component has a maintainer in the Dapr community or the Dapr maintainers
-- The component is well documented, tested and maintained across multiple versions of components-contrib repo
+- The component must have component [certification tests](#certification-tests) validating functionality and resiliency
+- The component is maintained by Dapr maintainers and supported by the community
+- The component is well documented and tested
+- A maintainer will address component security, core functionality and test issues according to the Dapr support policy and issue a patch release that includes the patched stable component
+
+### Previous Generally Available (GA) components
+
+Any component that was previously certified as GA is allowed into Stable even if the new requirements are not met.
## Conformance tests
@@ -66,24 +71,45 @@ To understand more about them see the readme [here](https://github.com/dapr/comp
- The tests should validate the functional behavior and robustness of component based on the component specification
- All the details needed to reproduce the tests are added as part of the component conformance test documentation
+## Certification tests
+
+Each stable component in the [components-contrib](https://github.com/dapr/components-contrib) repository must have a certification test plan and automated certification tests validating all features supported by the component via Dapr.
+
+Test plan for stable components should include the following scenarios:
+
+- Client reconnection: in case the client library cannot connect to the service for a moment, Dapr sidecar should not require a restart once the service is back online.
+- Authentication options: validate the component can authenticate with all the supported options.
+- Validate resource provisioning: validate if the component automatically provisions resources on initialization, if applicable.
+- All scenarios relevant to the corresponding building block and component.
+
+The test plan must be approved by a Dapr maintainer and be published in a `README.md` file along with the component code.
+
+### Test requirements
+
+- The tests should validate the functional behavior and robustness of the component based on the component specification, reflecting the scenarios from the test plan
+- The tests must run successfully as part of the continuous integration of the [components-contrib](https://github.com/dapr/components-contrib) repository
+
+
## Component certification process
-For a component to be certified tests are run in an environment maintained by the Dapr team.
+In order for a component to be certified, tests are run in an environment maintained by the Dapr project.
-### New component certification: Alpha->Beta or Beta->GA
+### New component certification: Alpha->Beta
-For a new component requiring a certification change from Alpha to Beta or Beta to GA, a request for component certification follows these steps:
-- An issue is created with a request for certification of the component with the current and the new certification levels
-- A user of a component submits a PR for integrating the component to run with the defined conformance test suite
-- The user details the environment setup in the issue created, so that a Dapr maintainer can setup the service in a managed environment
-- After the environment setup is complete, Dapr maintainers review the PR and if approved merges that PR
-- Dapr maintainers review functional correctness with the test being run in an environment maintained by the Dapr team
-- Dapr maintainers update the component status document categorized by Dapr Runtime version. This is done as part of the release process in the next release of Dapr runtime
-
-### Existing GA certified component
-
-For an existing GA certified component, conformance test should be run against any changes made to component code or the backing service version or the client version.
-
-In the scenarios where a component version is updated, the component again starts from Alpha stage and then the new component certification is followed for that.
+For a new component requiring a certification change from Alpha to Beta, a request for component certification follows these steps:
+- Requestor creates an issue in the [components-contrib](https://github.com/dapr/components-contrib) repository for certification of the component with the current and the new certification levels
+- Requestor submits a PR to integrate the component with the defined conformance test suite, if not already included
+ - The user details the environment setup in the issue created, so a Dapr maintainer can setup the service in a managed environment
+ - After the environment setup is complete, Dapr maintainers review the PR and if approved merges that PR
+- Requestor submits a PR in the [docs](https://github.com/dapr/docs) repository, updating the component's certification level
+### New component certification: Beta->Stable
+For a new component requiring a certification change from Beta to Stable, a request for component certification follows these steps:
+- Requestor creates an issue in the [components-contrib](https://github.com/dapr/components-contrib) repository for certification of the component with the current and the new certification levels
+- Requestor submits a PR for the test plan as a `README.md` file in the component's source code directory
+ - The requestor details the test environment requirements in the created PR, including any manual steps or credentials needed
+ - A Dapr maintainer reviews the test plan, provides feedback or approves it, and eventually merges the PR
+- Requestor submits a PR for the automated certification tests, including scripts to provision resources when applicable
+- After the test environment setup is completed and credentials provisioned, Dapr maintainers review the PR and, if approved, merges the PR
+- Requestor submits a PR in the [docs](https://github.com/dapr/docs) repository, updating the component's certification level
diff --git a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-aks.md b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-aks.md
index 905ef73b7..0323ba208 100644
--- a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-aks.md
+++ b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-aks.md
@@ -12,7 +12,7 @@ description: >
## Prerequisites
- [Docker](https://docs.docker.com/install/)
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Azure CLI](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest)
## Deploy an Azure Kubernetes Service cluster
diff --git a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-gke.md b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-gke.md
index 5a7b7607c..53d278669 100644
--- a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-gke.md
+++ b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-gke.md
@@ -8,7 +8,7 @@ description: "Setup a Google Kubernetes Engine cluster"
### Prerequisites
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Google Cloud SDK](https://cloud.google.com/sdk)
## Create a new cluster
diff --git a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-minikube.md b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-minikube.md
index ef1d0110d..09762c9fd 100644
--- a/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-minikube.md
+++ b/daprdocs/content/en/operations/hosting/kubernetes/cluster/setup-minikube.md
@@ -12,7 +12,7 @@ description: >
## Prerequisites
- [Docker](https://docs.docker.com/install/)
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Minikube](https://minikube.sigs.k8s.io/docs/start/)
> Note: For Windows, enable Virtualization in BIOS and [install Hyper-V](https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
diff --git a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md
index afa7a238a..81b62d716 100644
--- a/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md
+++ b/daprdocs/content/en/operations/hosting/kubernetes/kubernetes-deploy.md
@@ -15,7 +15,7 @@ For more information on what is deployed to your Kubernetes cluster read the [Ku
## Prerequisites
- Install [Dapr CLI]({{< ref install-dapr-cli.md >}})
-- Install [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- Install [kubectl](https://kubernetes.io/docs/tasks/tools/)
- Kubernetes cluster (see below if needed)
### Create cluster
diff --git a/daprdocs/content/en/operations/monitoring/logging/fluentd.md b/daprdocs/content/en/operations/monitoring/logging/fluentd.md
index 0c15c1584..fd0758418 100644
--- a/daprdocs/content/en/operations/monitoring/logging/fluentd.md
+++ b/daprdocs/content/en/operations/monitoring/logging/fluentd.md
@@ -9,7 +9,7 @@ description: "How to install Fluentd, Elastic Search, and Kibana to search logs
## Prerequisites
- Kubernetes (> 1.14)
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Helm 3](https://helm.sh/)
## Install Elastic search and Kibana
diff --git a/daprdocs/content/en/operations/monitoring/metrics/azure-monitor.md b/daprdocs/content/en/operations/monitoring/metrics/azure-monitor.md
index 852716e76..c253d4f42 100644
--- a/daprdocs/content/en/operations/monitoring/metrics/azure-monitor.md
+++ b/daprdocs/content/en/operations/monitoring/metrics/azure-monitor.md
@@ -10,7 +10,7 @@ description: "Enable Dapr metrics and logs with Azure Monitor for Azure Kubernet
- [Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/)
- [Enable Azure Monitor For containers in AKS](https://docs.microsoft.com/en-us/azure/azure-monitor/insights/container-insights-overview)
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Helm 3](https://helm.sh/)
## Enable Prometheus metric scrape using config map
diff --git a/daprdocs/content/en/operations/monitoring/metrics/prometheus.md b/daprdocs/content/en/operations/monitoring/metrics/prometheus.md
index b81f1f539..b179b75a0 100644
--- a/daprdocs/content/en/operations/monitoring/metrics/prometheus.md
+++ b/daprdocs/content/en/operations/monitoring/metrics/prometheus.md
@@ -67,7 +67,7 @@ Once Prometheus is running, you'll be able to visit its dashboard by visiting `h
### Prerequisites
- Kubernetes (> 1.14)
-- [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/)
+- [kubectl](https://kubernetes.io/docs/tasks/tools/)
- [Helm 3](https://helm.sh/)
### Install Prometheus
diff --git a/daprdocs/content/en/operations/support/support-release-policy.md b/daprdocs/content/en/operations/support/support-release-policy.md
index 5ec7285f2..a07e40e4e 100644
--- a/daprdocs/content/en/operations/support/support-release-policy.md
+++ b/daprdocs/content/en/operations/support/support-release-policy.md
@@ -42,7 +42,9 @@ The table below shows the versions of Dapr releases that have been tested togeth
| Jul 26th 2021 | 1.3 | 1.3.0 | Java 1.2.0 Go 1.2.0 PHP 1.1.0 Python 1.2.0 .NET 1.3.0 | 0.7.0 | Supported |
| Sep 14th 2021 | 1.3.1 | 1.3.0 | Java 1.2.0 Go 1.2.0 PHP 1.1.0 Python 1.2.0 .NET 1.3.0 | 0.7.0 | Supported |
| Sep 15th 2021 | 1.4 | 1.4.0 | Java 1.3.0 Go 1.3.0 PHP 1.2.0 Python 1.3.0 .NET 1.4.0 | 0.8.0 | Supported |
-| Sep 22nd 2021 | 1.4.1 | 1.4.0 | Java 1.3.0 Go 1.3.0 PHP 1.2.0 Python 1.3.0 .NET 1.4.0 | 0.8.0 | Supported (current) |
+| Sep 22nd 2021 | 1.4.1 | 1.4.0 | Java 1.3.0 Go 1.3.0 PHP 1.2.0 Python 1.3.0 .NET 1.4.0 | 0.8.0 | Supported
+| Sep 24th 2021 | 1.4.2 | 1.4.0 | Java 1.3.0 Go 1.3.0 PHP 1.2.0 Python 1.3.0 .NET 1.4.0 | 0.8.0 | Supported |
+| Oct 7th 2021 | 1.4.3 | 1.4.0 | Java 1.3.0 Go 1.3.0 PHP 1.2.0 Python 1.3.0 .NET 1.4.0 | 0.8.0 | Supported (current) |
## Upgrade paths
After the 1.0 release of the runtime there may be situations where it is necessary to explicitly upgrade through an additional release to reach the desired target. For example an upgrade from v1.0 to v1.2 may need go pass through v1.1
@@ -56,16 +58,16 @@ General guidance on upgrading can be found for [self hosted mode]({{}})
* List of [pub/sub components]({{< ref supported-pubsub.md >}})
* List of [secret store components]({{< ref supported-secret-stores.md >}})
diff --git a/daprdocs/content/en/operations/troubleshooting/common_issues.md b/daprdocs/content/en/operations/troubleshooting/common_issues.md
index 77d963c80..f63e0d54d 100644
--- a/daprdocs/content/en/operations/troubleshooting/common_issues.md
+++ b/daprdocs/content/en/operations/troubleshooting/common_issues.md
@@ -226,3 +226,26 @@ In order for mDNS to function properly, ensure `Micorosft Content Filter` is ina
Microsoft Content Filter is disabled when the output is "Success".
> Some organizations will re-enable the filter from time to time. If you repeatedly encounter app-id values missing, first check to see if the filter has been re-enabled before doing more extensive troubleshooting.
+
+## Admission webhook denied the request
+
+You may encounter an error similar to the one below due to admission webhook having an allowlist for service accounts to create or modify resources.
+
+```
+root:[dapr]$ kubectl run -i --tty --rm debug --image=busybox --restart=Never -- sh
+Error from server: admission webhook "sidecar-injector.dapr.io" denied the request: service account 'user-xdd5l' not on the list of allowed controller accounts
+```
+
+To resolve this error, you should create a `clusterrolebind` for the current user:
+
+```bash
+kubectl create clusterrolebinding dapr-