Improve info about virtlet installation validation

[jellonek]

This change is 

[ivan4th]

Review status: 0 of 3 files reviewed at latest revision, 7 unresolved discussions.

---

deploy/real-cluster.md, line 80 at r1 (raw file):

Escape character is ^]

### Validation of ssh access to pod

Verifying ssh access to a VM pod

---

deploy/real-cluster.md, line 97 at r1 (raw file):

Validation of pod access to cluster services

Verifying accessing services from a VM pod

---

deploy/real-cluster.md, line 101 at r1 (raw file):

After connecting to VM using one of above method you can validate VM access to
cluster services. Use below command to display an IP address of kubernetes
api service:

After connecting to the VM using one of the above methods you can check access from the VM to cluster services. To check DNS resolution of cluster services, use the following command:

---

deploy/real-cluster.md, line 107 at r1 (raw file):

Use below command to try to access this service:

The following command may be used to check service connectivity (note that it'll give you an authentication error):

---

deploy/real-cluster.md, line 113 at r1 (raw file):

Using the same method you can verify access to any service from internet, e.x.:

You can also verify Internet access from the VM:

---

deploy/real-cluster.md, line 116 at r1 (raw file):

curl -k https://google.com

Also add ping -c 1 8.8.8.8

---

deploy/real-cluster.md, line 117 at r1 (raw file):

curl -k https://google.com

If you have Kubernetes Dashboard installed (it's present in kubeadm-dind-cluster installations for example), you can check dashboard access using this command:

curl http://kubernetes-dashboard.kube-system.svc.cluster.local

This should display some html from the dashboard's main page.

---

Comments from Reviewable

[jellonek]

Review status: 0 of 3 files reviewed at latest revision, 7 unresolved discussions.

---

deploy/real-cluster.md, line 80 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

Verifying ssh access to a VM pod

Done.

---

deploy/real-cluster.md, line 101 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

After connecting to the VM using one of the above methods you can check access from the VM to cluster services. To check DNS resolution of cluster services, use the following command:

Done.

---

deploy/real-cluster.md, line 107 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

The following command may be used to check service connectivity (note that it'll give you an authentication error):

Done.

---

deploy/real-cluster.md, line 113 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

You can also verify Internet access from the VM:

Done.

---

deploy/real-cluster.md, line 116 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

Also add ping -c 1 8.8.8.8

Done.

---

deploy/real-cluster.md, line 117 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

If you have Kubernetes Dashboard installed (it's present in kubeadm-dind-cluster installations for example), you can check dashboard access using this command:

curl http://kubernetes-dashboard.kube-system.svc.cluster.local

This should display some html from the dashboard's main page.

Done.

---

Comments from Reviewable

[ivan4th]

Reviewed 1 of 3 files at r1.
Review status: 1 of 3 files reviewed at latest revision, 1 unresolved discussion.

---

deploy/real-cluster.md, line 55 at r2 (raw file):

## Testing the installation

### Validation of basic pod starting

Sorry, missed this one. Should be "Checking basic pod startup"

---

Comments from Reviewable

[jellonek]

Reviewed 1 of 3 files at r1, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

---

deploy/real-cluster.md, line 97 at r1 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

Verifying accessing services from a VM pod

Done.

---

deploy/real-cluster.md, line 55 at r2 (raw file):

Previously, ivan4th (Ivan Shvedunov) wrote…

Sorry, missed this one. Should be "Checking basic pod startup"

Done.

---

Comments from Reviewable

[ivan4th]

Reviewed 1 of 3 files at r1, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable

[ivan4th]

---

Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable

[ologvinova]

---

Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable