New yugabyte db on kubernetes statefulsets does not wait for service cname init

[rkarthik007]

Hitting a few of these initially when starting a cluster, but it eventually goes away (just needed to wait a bit). Looks like the cname init for services in k8s takes some time, yb should wait for that gracefully.

*** SIGSEGV (@0x0) received by PID 1 (TID 0x7f1b72ea9a40) from PID 0; stack trace: ***
    @     0x7f1b68ce5ba0 (unknown)
    @     0x7f1b6896d566 __GI_abort
    @     0x7f1b6cc2393d yb::(anonymous namespace)::DumpStackTraceAndExit()
    @     0x7f1b6bdf50cd google::LogMessage::Fail()
    @     0x7f1b6bdf6fdd google::LogMessage::SendToLog()
    @     0x7f1b6bdf4c2a google::LogMessage::Flush()
    @     0x7f1b6bdf7a9f google::LogMessageFatal::~LogMessageFatal()
    @     0x7f1b6cc5324a yb::HostPort::ResolveAddresses()
    @     0x7f1b707f4b35 yb::server::ServerBaseOptions::DetermineMasterAddresses()
    @     0x7f1b72a3c196 yb::master::MasterOptions::CreateMasterOptions()
    @           0x40636d yb::master::MasterMain()
    @     0x7f1b68959825 __libc_start_main
    @           0x406069 _start
    @                0x0 (unknown)

[ttyusupov]

Same as #97 fixed by 40786a4