You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting a Verify hub & stubs running on Kubernetes
available deployments
deployment
status
stub-idp & database
tested successfully with a local [external] hub
frontend
app starts but needs a hub running
test-rp-msa
won't start due to config file
test-rp
won't start due to config file
config
won't start due to missing federation config files
saml-soap-proxy
won't start due to config file
saml-proxy
won't start due to config file
saml-engine
won't start due to config file
policy
won't start due to config file
stub-event-sink
starts
useful commands
install minikube
minikube sets up a local kubernetes
$ brew cask install minikube
run minikube
$ minikube start and wait for a few minutes
$ kubectl cluster-info will show information about the kubernetes cluster
$ minikube stop will stop the cluster and keep state
$ minikube delete will stop the cluster and delete all state
see the minikube dashboard
$ minikube dashboard will open the dashboard in your browser
run stub-idp and stub-idp-database
$ kubectl apply -f deployments/stub-idp.yaml
$ kubectl get pods -l app=stub-idp will list the running apps
$ kubectl delete -f deployments/stub-idp.yaml if it goes wrong
$ kubectl describe services stub-idp-service will show information about the running Service - note the NodePort that is used to access stub-idp outside kubernetes
$ curl $(minikube ip):30010/service-name should get the stub-idp service name from one of the apps
$ open $(minikube ip):30010/stub-country/login will display the something went wrong page