This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
API server --standalone-mode doesn't work
#364
Labels
Comments
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 17, 2018
* Tried to separate out the API server options that require kubernetes API configuration options. * Don't apply those command line options if `--standalone-mode` has been supplied. * Added a wrapper around the Kubernetes integration test framework to also launch the Navigator API server and connect it to the same Etcd server. * Currently parses stderr to check for a successful startup message, but the API server ought to have an `/healthz` endpoint. Fixes: jetstack#364
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 21, 2018
* Tried to separate out the API server options that require kubernetes API configuration options. * Don't apply those command line options if `--standalone-mode` has been supplied. * Added a wrapper around the Kubernetes integration test framework to also launch the Navigator API server and connect it to the same Etcd server. * Currently parses stderr to check for a successful startup message, but the API server ought to have an `/healthz` endpoint. Fixes: jetstack#364 Hook up a navigator cli helper
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Trying to run the navigator API server locally but found that even with the
--standalone-modeflag, it still requires Kubernetes API host, port and token./kind bug
The text was updated successfully, but these errors were encountered: