Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additions to the master cert via a SANS entry should be possible. #2459

Closed
snoby opened this issue Apr 28, 2017 · 3 comments
Closed

Additions to the master cert via a SANS entry should be possible. #2459

snoby opened this issue Apr 28, 2017 · 3 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@snoby
Copy link
Contributor

snoby commented Apr 28, 2017

It should be possible to add an additional DNS names to the SANS portion of the master cert. Besides the entry of the additional name via #2063 , we need for kops to handle distributing that updated cert to all the elements. Elements like the api servers and perhaps the worker nodes?

The use case is after a deployment where master and minions are private I change the API server ELB to an Internal Only ELB and then I only have access via a bastion / jump server. On that jump server I will be running nginx doing TCP proxying. This bastion is internal to my companies home network, so basically everything in kubernetes is internal except the ingress ELB.

Tagging Chris because he wanted to be tagged and Kris because we had talked about it in the past.
@chrislovecnm @kris-nova @justinsb

@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 23, 2017
@fejta-bot
Copy link

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
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 22, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants