Should there be a warning in the vault config about this? This resulted in a non-obvious issue. Maybe surface something better than "Waiting for kube-proxy to start" to get people on the right path? Leaving this bug for that type of discussion.
Had to nuke the app and add it again, but it started up fine after that.
sad_panda.jpg
Should there be a warning in the vault config about this? This resulted in a non-obvious issue. Maybe surface something better than "Waiting for kube-proxy to start" to get people on the right path? Leaving this bug for that type of discussion.
Had to nuke the app and add it again, but it started up fine after that.