Skip to content
This repository has been archived by the owner on Dec 5, 2017. It is now read-only.

Use https from kubectl through the admin router to the apiserver #535

Closed
3 tasks done
sttts opened this issue Oct 5, 2015 · 5 comments
Closed
3 tasks done

Use https from kubectl through the admin router to the apiserver #535

sttts opened this issue Oct 5, 2015 · 5 comments

Comments

@sttts
Copy link

sttts commented Oct 5, 2015

As a user I want to

  • have kubectl exec & log to work
  • have a secure connection between my local machine and the apiserver.

TODO:

  • implement TLS support for the apiserver
  • look into the admin router implementation
  • prototype a config change to allow SPDY
@sttts sttts added this to the EPIC: blockers for k8s production-readiness milestone Oct 5, 2015
@sttts
Copy link
Author

sttts commented Oct 5, 2015

cc @karlkfi

@sttts
Copy link
Author

sttts commented Oct 13, 2015

If I understand the SPDY support correctly, SPDY depends on HTTPS. To get HTTPS in DCOS we need certificate generation and probably service accounts.

@sttts
Copy link
Author

sttts commented Oct 14, 2015

Not sure I understood the CM.3 demo correctly: does it bring SSL admin router support?

@sttts
Copy link
Author

sttts commented Oct 19, 2015

This is blocked until we deploy TLS, service accounts etc. #409

@sttts sttts removed the priority/P1 label Oct 19, 2015
@sttts sttts modified the milestones: Minimum Viable Product (MVP), Production Readiness Oct 23, 2015
@sttts sttts changed the title kubectl exec+log not working with admin router Support kubectl exec+log with admin router Oct 23, 2015
@sttts sttts changed the title Support kubectl exec+log with admin router Use https from kubectl through the admin router to the apiserver Oct 23, 2015
@jdef jdef added blocked and removed priority/soon labels Nov 3, 2015
@jdef
Copy link

jdef commented Nov 3, 2015

blocked by #555

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.