mirror of https://github.com/dapr/docs.git
Merge branch 'v1.12' into asb-metadata-bindings
This commit is contained in:
Hannah Hunter
GitHub
commit
9971ee59bb
|
|
@ -6,24 +6,24 @@ weight: 15
|
|||
description: "List of Dapr bot capabilities."
|
||||
---
|
||||
|
||||
Dapr bot is a GitHub script that helps with common tasks in the Dapr organization. It is set up individually for each repository ([example](https://github.com/dapr/dapr/blob/master/.github/workflows/dapr-bot.yml)) and can be configured to run on specific events. This reference covers the Dapr bot capabilities from the `dapr` and `components-contrib` repositories only.
|
||||
Dapr bot is triggered by a list of commands that helps with common tasks in the Dapr organization. It is set up individually for each repository ([example](https://github.com/dapr/dapr/blob/master/.github/workflows/dapr-bot.yml)) and can be configured to run on specific events. Below is a list of commands and the list of repositories they are implemented on.
|
||||
|
||||
## Command reference
|
||||
|
||||
| Command | Target | Description | Who can use | Repository |
|
||||
|---------|--------|-------------|-------------|------------|
|
||||
| `/assign` | Issue | Assigns an issue to a user or group of users | Anyone | `dapr`, `components-contrib` |
|
||||
| `/ok-to-test` | Pull request | `dapr`: trigger end to end tests <br/> `components-contrib`: trigger conformance and certification tests | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr`, `components-contrib` |
|
||||
| `/ok-to-perf` | Pull request | Trigger performance tests. | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr` |
|
||||
| `/make-me-laugh` | Issue or pull request | Posts a random joke | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr`, `components-contrib` |
|
||||
| Command | Target | Description | Who can use | Repository |
|
||||
| ---------------- | --------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------- |
|
||||
| `/assign` | Issue | Assigns an issue to a user or group of users | Anyone | `dapr`, `components-contrib`, `go-sdk` |
|
||||
| `/ok-to-test` | Pull request | `dapr`: trigger end to end tests <br/> `components-contrib`: trigger conformance and certification tests | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr`, `components-contrib` |
|
||||
| `/ok-to-perf` | Pull request | Trigger performance tests. | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr` |
|
||||
| `/make-me-laugh` | Issue or pull request | Posts a random joke | Users listed in the [bot](https://github.com/dapr/dapr/blob/master/.github/scripts/dapr_bot.js) | `dapr`, `components-contrib` |
|
||||
|
||||
## Label reference
|
||||
|
||||
You can query issues created by the Dapr bot by using the `created-by/dapr-bot` label ([query](https://github.com/search?q=org%3Adapr%20is%3Aissue%20label%3Acreated-by%2Fdapr-bot%20&type=issues)).
|
||||
|
||||
| Label | Target | What does it do? | Repository |
|
||||
|-------|--------|------------------|------------|
|
||||
| `docs-needed` | Issue | Creates a new issue in `dapr/docs` to track doc work | `dapr` |
|
||||
| `sdk-needed` | Issue | Creates new issues across the SDK repos to track SDK work | `dapr` |
|
||||
| `documentation required` | Issue or pull request | Creates a new issue in `dapr/docs` to track doc work | `components-contrib` |
|
||||
| `new component` | Issue or pull request | Creates a new issue in `dapr/dapr` to register the new component | `components-contrib` |
|
||||
| Label | Target | What does it do? | Repository |
|
||||
| ------------------------ | --------------------- | ---------------------------------------------------------------- | -------------------- |
|
||||
| `docs-needed` | Issue | Creates a new issue in `dapr/docs` to track doc work | `dapr` |
|
||||
| `sdk-needed` | Issue | Creates new issues across the SDK repos to track SDK work | `dapr` |
|
||||
| `documentation required` | Issue or pull request | Creates a new issue in `dapr/docs` to track doc work | `components-contrib` |
|
||||
| `new component` | Issue or pull request | Creates a new issue in `dapr/dapr` to register the new component | `components-contrib` |
|
||||
|
|
|
|||
|
|
@ -219,7 +219,7 @@ namespace CheckoutService.controller
|
|||
Navigate to the directory containing the above code, then run the following command to launch both a Dapr sidecar and the subscriber application:
|
||||
|
||||
```bash
|
||||
dapr run --app-id checkout --app-port 6002 --dapr-http-port 3602 --dapr-grpc-port 60002 --app-ssl dotnet run
|
||||
dapr run --app-id checkout --app-port 6002 --dapr-http-port 3602 --dapr-grpc-port 60002 --app-protocol https dotnet run
|
||||
```
|
||||
|
||||
{{% /codetab %}}
|
||||
|
|
@ -465,7 +465,7 @@ namespace EventService
|
|||
Navigate to the directory containing the above code, then run the following command to launch both a Dapr sidecar and the publisher application:
|
||||
|
||||
```bash
|
||||
dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-grpc-port 60001 --app-ssl dotnet run
|
||||
dapr run --app-id orderprocessing --app-port 6001 --dapr-http-port 3601 --dapr-grpc-port 60001 --app-protocol https dotnet run
|
||||
```
|
||||
|
||||
{{% /codetab %}}
|
||||
|
|
|
|||
|
|
@ -201,7 +201,7 @@ helm repo add dapr https://dapr.github.io/helm-charts/
|
|||
helm repo update
|
||||
kubectl create namespace dapr-system
|
||||
# Install the Dapr dashboard
|
||||
helm install dapr dapr/dapr-dashboard --namespace dapr-system
|
||||
helm install dapr-dashboard dapr/dapr-dashboard --namespace dapr-system
|
||||
```
|
||||
|
||||
### Verify installation
|
||||
|
|
|
|||
|
|
@ -74,6 +74,7 @@ spec:
|
|||
| `oidcScopes` | N | Input/Output | Comma-delimited list of OAuth2/OIDC scopes to request with the access token. Recommended when `authType` is set to `oidc`. Defaults to `"openid"` | `"openid,kafka-prod"` |
|
||||
| `version` | N | Input/Output | Kafka cluster version. Defaults to 2.0.0. Please note that this needs to be mandatorily set to `1.0.0` for EventHubs with Kafka. | `"1.0.0"` |
|
||||
| `direction` | N | Input/Output | The direction of the binding. | `"input"`, `"output"`, `"input, output"` |
|
||||
| `oidcExtensions` | N | Input/Output | String containing a JSON-encoded dictionary of OAuth2/OIDC extensions to request with the access token | `{"cluster":"kafka","poolid":"kafkapool"}` |
|
||||
|
||||
#### Note
|
||||
The metadata `version` must be set to `1.0.0` when using Azure EventHubs with Kafka.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,22 @@ description: Detailed information on the Kubernetes DNS name resolution componen
|
|||
|
||||
## Configuration format
|
||||
|
||||
Kubernetes DNS name resolution is configured automatically in [Kubernetes mode]({{< ref kubernetes >}}) by Dapr. There is no configuration needed to use Kubernetes DNS as your name resolution provider.
|
||||
Generally, Kubernetes DNS name resolution is configured automatically in [Kubernetes mode]({{< ref kubernetes >}}) by Dapr. There is no configuration needed to use Kubernetes DNS as your name resolution provider unless some overrides are necessary for the Kubernetes name resolution component.
|
||||
|
||||
In the scenario that an override is required, within a [Dapr Configuration]({{< ref configuration-overview.md >}}) CRD, add a `nameResolution` spec and set the `component` field to `"kubernetes"`. The other configuration fields can be set as needed in a `configuration` map, as seen below.
|
||||
|
||||
```yaml
|
||||
apiVersion: dapr.io/v1alpha1
|
||||
kind: Configuration
|
||||
metadata:
|
||||
name: appconfig
|
||||
spec:
|
||||
nameResolution:
|
||||
component: "kubernetes"
|
||||
configuration:
|
||||
clusterDomain: "cluster.local" # Mutually exclusive with the template field
|
||||
template: "{{.ID}}-{{.Data.region}}.internal:{{.Port}}" # Mutually exclusive with the clusterDomain field
|
||||
```
|
||||
|
||||
## Behaviour
|
||||
|
||||
|
|
@ -15,7 +30,13 @@ The component resolves target apps by using the Kubernetes cluster's DNS provide
|
|||
|
||||
## Spec configuration fields
|
||||
|
||||
Not applicable, as Kubernetes DNS is configured by Dapr when running in Kubernetes mode.
|
||||
The configuration spec is fixed to v1.3.0 of the Consul API
|
||||
|
||||
| Field | Required | Type | Details | Examples |
|
||||
|--------------|:--------:|-----:|:---------|----------|
|
||||
| clusterDomain | N | `string` | The cluster domain to be used for resolved addresses. This field is mutually exclusive with the `template` file.| `cluster.local`
|
||||
| template | N | `string` | A template string to be parsed when addresses are resolved using [text/template](https://pkg.go.dev/text/template#Template) . The template will be populated by the fields in the [ResolveRequest](https://github.com/dapr/components-contrib/blob/release-{{% dapr-latest-version short="true" %}}/nameresolution/requests.go#L20) struct. This field is mutually exclusive with `clusterDomain` field. | `{{.ID}}-{{.Data.region}}.{{.Namespace}}.internal:{{.Port}}`
|
||||
|
||||
|
||||
## Related links
|
||||
|
||||
|
|
|
|||
|
|
@ -80,6 +80,7 @@ spec:
|
|||
| oidcClientID | N | The OAuth2 client ID that has been provisioned in the identity provider. Required when `authType` is set to `oidc` | `dapr-kafka` |
|
||||
| oidcClientSecret | N | The OAuth2 client secret that has been provisioned in the identity provider: Required when `authType` is set to `oidc` | `"KeFg23!"` |
|
||||
| oidcScopes | N | Comma-delimited list of OAuth2/OIDC scopes to request with the access token. Recommended when `authType` is set to `oidc`. Defaults to `"openid"` | `"openid,kafka-prod"` |
|
||||
| oidcExtensions | N | Input/Output | String containing a JSON-encoded dictionary of OAuth2/OIDC extensions to request with the access token | `{"cluster":"kafka","poolid":"kafkapool"}` |
|
||||
|
||||
The `secretKeyRef` above is referencing a [kubernetes secrets store]({{< ref kubernetes-secret-store.md >}}) to access the tls information. Visit [here]({{< ref setup-secret-store.md >}}) to learn more about how to configure a secret store component.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue