Open medyagh opened 4 years ago
@alanbrent could you share the yaml files and all the configurations as you do it manually to setup ha proxy ?
(Updated w/ Namespace and default backend bits)
Here you go. Note that the TLS bits aren't actually sensitive, it's just a self-signed cert I generated to satisfy whatever cargo culting I was doing :)
I would imagine that constructing your tests around the ingress-controller minikube addon would be a much easier path to achieve the desired testing, but I may not fully understand what you're looking to achieve here :)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
/lifecycle frozen
(Continuing from a #minikube Slack convo)
At a high level, we do the following at our org:
haproxy
for no good reason, any Ingress Controller will do including I assume aminikube
ingress addon)So again at a high level, one could test this by standing those things up and then issuing a
curl -H 'Host: $APP_SVC_NAME.$K8S_NAMESPACE.svc.cluster.local' $MINIKUBE_IP/test_path_eg_healthz
.It's not a script, but hopefully the high level description is useful.