[16:52:22] <ebernhardson>	 one of our releases has an administrative api that is occasionally needed.  I can `kubectl port-forward` or `kubectl exec` to get access to it, but have to swap out KUBECONFIG to the deployment config for those to work.  Is there a better way for exposing an administrative port for a release? Perhaps something that magick's up a domain name from the release/namespace?
[17:07:19] <ebernhardson>	 The use case is that during a proceedure that is repeated ~3k times over a few days it needs to submit something and then watch the api for it to be reported complete
[17:37:25] <inflatador>	 ebernhardson would it make sense to push the app status to kafka and have it read from there?
[17:39:05] <ebernhardson>	 inflatador: i'm not sure we can, what we are polling for is the flink jobmanager to say the task is completed, we don't really have any ability to do anything there. Additionally the thing polling will be a bash script (or maybe cookbook), from which kafka will be tedious to watch
[17:40:18] <inflatador>	 ebernhardson interesting...I wonder if we could figure that out from the ZK metadata?
[17:40:34] <ebernhardson>	 inflatador: that sounds even more tedious to query :)