timeout for overlord and discovery about corekube HOT 2 CLOSED

Thank you for the kind words and the report that you're experiencing a timeout.

Could you please specify where you're in the process that you're seeing the timeout, as well as, include any logs or information that could help me recreate the problem?

The corekube-openstack.yaml stack has been tested & does work for a private install via openstack-ansible, but the system used is based on an older deployment of it which should be updated; nevertheless, the OpenStack components used are Glance, Nova, Neutron and Heat, so as long as those all functional there shouldn't be a reason for any timeout.

from corekube.

so it seems like the cluster is up and operational. i may have created this issue a little too quickly, or as things were still building out. i read more about the overload node, and i think i get it a little better now. thanks for the quick reply, sorry for not getting back to you sooner. i have some questions about your thoughts on SDN (related to CNI) and service exposure, but I may just try to hit you up on k8s Slack if you don't mind? great job...nice, clean deployment/repo!

from corekube.