You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-nexus/troubleshoot-dns-issues.md
+18-5Lines changed: 18 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,20 +17,33 @@ cluster running on Azure VMs (Virtual Machines) and Azure, accessing Azure resou
17
17
domain names. However a DNS (Domain Name System) error in NNF can mean that Azure resources
18
18
can't be contacted which impacts deployment or management of Nexus resources.
19
19
20
+
The DNS proxy that causes this error is an [Envoy DNS Proxy](https://www.envoyproxy.io/docs/envoy/latest/)
21
+
running via a Kubernetes deployment in either an Infrastructure or Tenant cluster.
22
+
The precise location of the DNS proxy will have been determined when the customer
23
+
has deployed ther NAKS (Nexus Azure Kubernetes Service) cluster or during some other
24
+
deployment.
25
+
20
26
## Diagnosis
21
27
22
28
* Deployment or management of remote Nexus resources fails with "DeploymentFailed."
23
29
* Azure portal shows no errors being generated for the Azure resources that are unreachable; there are no errors because the failing operations aren't reaching the Azure resources at all.
24
30
25
31
## Mitigation steps
26
32
27
-
Follow these steps for mitigation.
28
-
29
33
### Trigger a DNS cache refresh for the NNF Workload Proxy
30
-
34
+
35
+
- Based on configuration and deployment, identify the Infrastructure or Tenant Kubernetes Cluster on which the DNS proxy is runnning
36
+
- Log-in to the Kubernetes cluster
37
+
- Using the Azure portal, find your cluster
38
+
- From the _Overview_ blade, click the _Connect_ command (between _Refresh_ and _Delete_)
39
+
- Follow the instructions from the resulting pop-up window that explains how to use Kubernetes cluster
40
+
- Identify the DNS proxy deployment using this command
41
+
```bash
42
+
$ kubectl get deployments --all-namespaces=true | grep envoy
43
+
```
44
+
- Restart the deployment, which will cause the DNS caching to be reset, using this command:
31
45
```bash
32
-
# TBD awaiting feedback from folks who worked on the original IcMs as to
0 commit comments