Connection Timeout from Worker node Kubernetes deployment for AIO-Duplex extended capacity scenario

[Yatindra]

Brief Description
-----------------
While installing Kubernetes-dashboard in AIO-Duplex extended capacity setup, kubernetes schedule pod in worker-0 but worker-0 is unable to downlod from docker registry
Severity
--------
Provide the severity of the defect.

Major: Major for Duplex- extended setup

Steps to Reproduce
------------------
Try to run kubernetes pods in the worker-0 node. Unable to pull the image.

Expected Behavior
------------------
Docker image downloaded and scheduled on worker-0

Actual Behavior
----------------
Was not able to download the docker image at worker-.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
AIO-Duplex extended capacity with proxy

Branch/Pull Time/Commit
-----------------------
STX 3.0 Stable release

Last Pass
---------

Timestamp/Logs
--------------

Output of command:
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl describe pod dashboard-metrics-scraper-7b8b58dc8b-2rf44 -n kubernetes-dashbo

xxxxx
xxxx
xxxxx

Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal Scheduled <unknown> default-scheduler Successfully assigned kubernetes-dashboard/dashboard-metrics-scraper-7b8b58dc8b-2rf44 to worker-0
  Normal Pulling 27s kubelet, worker-0 Pulling image "kubernetesui/metrics-scraper:v1.0.3"
  Warning Failed 12s kubelet, worker-0 Failed to pull image "kubernetesui/metrics-scraper:v1.0.3": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
  Warning Failed 12s kubelet, worker-0 Error: ErrImagePull
  Normal SandboxChanged 4s (x2 over 11s) kubelet, worker-0 Pod sandbox changed, it will be killed and re-created.
  Normal BackOff 4s kubelet, worker-0 Back-off pulling image "kubernetesui/metrics-scraper:v1.0.3"
  Warning Failed 4s kubelet, worker-0 Error: ImagePullBackOff

Test Activity
-------------

 Workaround
 ----------

Adding IP tables rules at active controller:

$sudo iptables -t nat -A POSTROUTING -p tcp -s 192.168.204.0/24 -j MASQUERADE

[Ghada Khalil (gkhalil)]

Added the domain & release tags. This will require further investigation from the containers team.
However, collect logs should be attached to enable the investigation.

[Ghada Khalil (gkhalil)]

Closing as stx.3.0 is EOL as of Dec 2020