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
Explicitly set scheme in node redirects
Plumb ports to support TLS
Generate self-signed certs, plumb in env vars to infrastructure pods
Add docker loopback to master cert
Make scheme and port configurable in e2e
Change default to SSL
Simplify bootstrapping
Move crypto package, persist serial numbers between starts, make helper functions private
Use generic crypto.PublicKey/PrivateKey interface
Build assets
Change OSC default scheme/port, generate .kubernetes_auth files
Doc update to TLS
Use .kubeconfig for cert config in tests
Override default server host to https://localhost:8443
Use api object to write .kubeconfig
OpenShift and Kubernetes integrate with the [Swagger 2.0 API framework](http://swagger.io) which aims to make it easier to document and write clients for RESTful APIs. When you start OpenShift, the Swagger API endpoint is exposed at `http://localhost:8080/swaggerapi`. The Swagger UI makes it easy to view your documentation - to view the docs for your local version of OpenShift start the server with CORS enabled:
160
+
OpenShift and Kubernetes integrate with the [Swagger 2.0 API framework](http://swagger.io) which aims to make it easier to document and write clients for RESTful APIs. When you start OpenShift, the Swagger API endpoint is exposed at `https://localhost:8443/swaggerapi`. The Swagger UI makes it easy to view your documentation - to view the docs for your local version of OpenShift start the server with CORS enabled:
0 commit comments