File tree Expand file tree Collapse file tree 1 file changed +1
-9
lines changed Expand file tree Collapse file tree 1 file changed +1
-9
lines changed Original file line number Diff line number Diff line change @@ -53,10 +53,6 @@ Error message in logs/events:
53
53
E1029 17:37:42.461313 1 server.go:54] failed to process mount request, error: keyvault.BaseClient#GetSecret: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
54
54
```
55
55
56
- <<<<<<< HEAD
57
- <<<<<<< HEAD
58
- =======
59
- >>>>>>> 49cb622d465041b17932527dc9841174845599e4
60
56
Description: The provider pod is unable to access the key vault instance for either of the following reasons:
61
57
- A firewall rule is blocking egress traffic from the provider.
62
58
- Network policies that are configured in the AKS cluster are blocking egress traffic.
@@ -103,8 +99,7 @@ You can test the connectivity to your Azure key vault from the pod that's runnin
103
99
` ` ` bash
104
100
curl -X GET 'https://<KEY_VAULT_NAME>.vault.azure.net/secrets/<SECRET_NAME>?api-version=7.2' -H "Authorization: Bearer <ACCESS_TOKEN_ACQUIRED_ABOVE>"
105
101
` ` `
106
- <<< <<< < HEAD
107
- =======
102
+
108
103
It means the provider pod is unable to access the AKV instance because:
109
104
110
105
- There is a firewall rule blocking egress traffic from the provider.
@@ -152,9 +147,6 @@ You can test Key Vault connectivity from pod running on host network as follows:
152
147
` ` ` bash
153
148
curl -X GET 'https://<KEY_VAULT_NAME>.vault.azure.net/secrets/<SECRET_NAME>?api-version=7.2' -H "Authorization: Bearer <ACCESS_TOKEN_ACQUIRED_ABOVE>"
154
149
` ` `
155
- >>>>>>> b90873b7593e0a387bf1a446e73da21779059895
156
- =======
157
- >>>>>>> 49cb622d465041b17932527dc9841174845599e4
158
150
159
151
< ! -- LINKS EXTERNAL -->
160
152
[aad-troubleshooting]: https://azure.github.io/aad-pod-identity/docs/troubleshooting/
You can’t perform that action at this time.
0 commit comments