[helm install] Pod don`t get ready

[fabiodoaraujo]

Install through helm chart with default values and the pod didn`t get read.

+ kube-opex-analytics-849ff45d4b-nt2qz › kube-opex-analytics kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics *** Starting uWSGI 2.0.18 (64bit) on [Tue Oct 29 14:00:19 2019] *** kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics compiled with version: 7.4.0 on 28 September 2019 14:43:37 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics os: Linux-4.15.0-43-generic #46~16.04.1-Ubuntu SMP Fri Dec 7 13:31:08 UTC 2018 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics nodename: kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics machine: x86_64 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics clock source: unix kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics detected number of CPU cores: 8 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics current working directory: /koa kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics detected binary path: /usr/local/bin/uwsgi kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics !!! no internal routing support, rebuild with pcre support !!! kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics your memory page size is 4096 bytes kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics detected max file descriptor number: 1048576 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics lock engine: pthread robust mutexes kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics thunder lock: disabled (you can enable it with --thunder-lock) kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics *** RRDtool library available at 0x55d9b0349a20 *** kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics uwsgi socket 0 bound to TCP address :5483 fd 3 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics Python version: 3.6.8 (default, Aug 20 2019, 17:12:48) [GCC 8.3.0] kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics Python main interpreter initialized at 0x55d9b037a660 kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics python threads support enabled kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics your server socket listen backlog is limited to 100 connections kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics your mercy for graceful operations on workers is 60 seconds kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics mapped 145808 bytes (142 KB) for 1 cores kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics *** Operational MODE: single process *** kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x55d9b037a660 pid: 9 (default app) kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics *** uWSGI is running in multiple interpreter mode *** kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics spawned uWSGI master process (pid: 9) kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics spawned uWSGI worker 1 (pid: 15, cores: 1) kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics /usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py:1004: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics InsecureRequestWarning, kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics /usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py:1004: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics InsecureRequestWarning, kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics /usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py:1004: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics InsecureRequestWarning, kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics /usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py:1004: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics InsecureRequestWarning, kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics /usr/local/lib/python3.6/dist-packages/urllib3/connectionpool.py:1004: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings kube-opex-analytics-849ff45d4b-nt2qz kube-opex-analytics InsecureRequestWarning,