dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add information about needed ports for kube api to reach (#3078) 

* add information about needed ports for kube api to reach

Signed-off-by: Filinto Duran <filinto@diagrid.io>

* correct identation of next paragraph

Signed-off-by: Filinto Duran <filinto@diagrid.io>
This commit is contained in:
Filinto Duran 2023-01-20 23:25:19 -06:00 committed by GitHub
parent 001e1fe2e0
commit 5c2c449cc3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 31 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
daprdocs/content/en/operations/troubleshooting/common_issues.md
View File

@ -50,45 +50,54 @@ spec:
imagePullPolicy: Always imagePullPolicy: Always
``` ```
If your pod spec template is annotated correctly and you still don't see the sidecar injected, make sure Dapr was deployed to the cluster before your deployment or pod were deployed. There are some known cases where this might not properly work:
If this is the case, restarting the pods will fix the issue. - If your pod spec template is annotated correctly, and you still don't see the sidecar injected, make sure Dapr was deployed to the cluster before your deployment or pod were deployed.
If you are deploying Dapr on a private GKE cluster, sidecar injection does not work without extra steps. See [Setup a Google Kubernetes Engine cluster]({{< ref setup-gke.md >}}). If this is the case, restarting the pods will fix the issue.
In order to further diagnose any issue, check the logs of the Dapr sidecar injector: - If you are deploying Dapr on a private GKE cluster, sidecar injection does not work without extra steps. See [Setup a Google Kubernetes Engine cluster]({{< ref setup-gke.md >}}).
```bash In order to further diagnose any issue, check the logs of the Dapr sidecar injector:
```bash
kubectl logs -l app=dapr-sidecar-injector -n dapr-system kubectl logs -l app=dapr-sidecar-injector -n dapr-system
``` ```
*Note: If you installed Dapr to a different namespace, replace dapr-system above with the desired namespace* *Note: If you installed Dapr to a different namespace, replace dapr-system above with the desired namespace*
If you are deploying Dapr on Amazon EKS and using an overlay network such as Calico, you will need to set `hostNetwork` parameter to true, this is a limitation of EKS with such CNIs. - If you are deploying Dapr on Amazon EKS and using an overlay network such as Calico, you will need to set `hostNetwork` parameter to true, this is a limitation of EKS with such CNIs.
You can set this parameter using Helm `values.yaml` file: You can set this parameter using Helm `values.yaml` file:
``` ```
helm upgrade --install dapr dapr/dapr \ helm upgrade --install dapr dapr/dapr \
--namespace dapr-system \ --namespace dapr-system \
--create-namespace \ --create-namespace \
--values values.yaml --values values.yaml
``` ```
`values.yaml` `values.yaml`
```yaml ```yaml
dapr_sidecar_injector: dapr_sidecar_injector:
hostNetwork: true hostNetwork: true
``` ```
or using command line: or using command line:
``` ```
helm upgrade --install dapr dapr/dapr \ helm upgrade --install dapr dapr/dapr \
--namespace dapr-system \ --namespace dapr-system \
--create-namespace \ --create-namespace \
--set dapr_sidecar_injector.hostNetwork=true --set dapr_sidecar_injector.hostNetwork=true
``` ```
- Make sure the kube api server can reach the following webhooks services:
- [Sidecar Mutating Webhook Injector Service](https://github.com/dapr/dapr/blob/44235fe8e8799589bb393a3124d2564db2dd6885/charts/dapr/charts/dapr_sidecar_injector/templates/dapr_sidecar_injector_deployment.yaml#L157) at port __4000__ that is served from the sidecar injector.
- [CRD Conversion Webhook Service](https://github.com/dapr/dapr/blob/44235fe8e8799589bb393a3124d2564db2dd6885/charts/dapr/charts/dapr_operator/templates/dapr_operator_service.yaml#L28) at port __19443__ that is served from the operator.
Check with your cluster administrators to setup allow ingress
rules to the above ports, __4000__ and __19443__, in the cluster from the kube api servers.
## My pod is in CrashLoopBackoff or another failed state due to the daprd sidecar ## My pod is in CrashLoopBackoff or another failed state due to the daprd sidecar