Hey Jeff Morris - any idea when you'll get a chance to get round to this? If it'll be more than a few days I'll take the cluster down and then I can spin it back up again whenever you're ready!
It's on AWS so just trying to be conscious of saving money.

Matt Carabine
added a comment - 23/Apr/19 3:05 PM - edited Hey Jeff Morris - any idea when you'll get a chance to get round to this? If it'll be more than a few days I'll take the cluster down and then I can spin it back up again whenever you're ready!
It's on AWS so just trying to be conscious of saving money.

My bad, Easter week and time off! I am backed up at the moment, so probably just better to power off and then Michael Goldsmith or myself can ping you (and the ticket to "in-progress" when we are ready to start working on it. Note the fox-release is more likely to be 2.7.8 and not 2.7.7 as indicated (will be updated soon).

Jeff Morris
added a comment - 23/Apr/19 3:11 PM Matt Carabine -
My bad, Easter week and time off! I am backed up at the moment, so probably just better to power off and then Michael Goldsmith or myself can ping you (and the ticket to "in-progress" when we are ready to start working on it. Note the fox-release is more likely to be 2.7.8 and not 2.7.7 as indicated (will be updated soon).
We really appreciate you setting up the enviorment on AWS!
Thanks,
Jeff

Michael Goldsmith: Jeff told me about the SDKQE testing planned on this one that you're working toward. Quick question: do you have confidence that the change works in the env. MattC had or a similar env.?

Matt Ingenthron
added a comment - 20/May/19 9:35 AM Michael Goldsmith : Jeff told me about the SDKQE testing planned on this one that you're working toward. Quick question: do you have confidence that the change works in the env. MattC had or a similar env.?

Matt Carabine
added a comment - 20/May/19 9:38 AM - edited My environment is using public connectivity (assuming this is how the fix is being verified).
Only place that I don't think has been tested is the NodePorts case where the alternate ports are also different too, but think this fix would cover both scenarios?

Jeff Morris
added a comment - 27/Jun/19 5:15 PM - edited Re-opening this because it triggers a regression defined in NCBC-2002 ; we'll need to revert this issue and come up with an alternative solution or patch it in the NCBC-2002 fix.
Matt Carabine - can you attach a cluster map from from a Kubernetes environment with non-resolvable hostnames?
Nevermind using attached ncbc_1927.txt.