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.

Sign up for GitHub

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

Jump to bottom

Document Authentication Configuration #236

Closed
ProTip opened this issue Aug 1, 2016 · 4 comments
Closed

Document Authentication Configuration #236

ProTip opened this issue Aug 1, 2016 · 4 comments
Assignees
@justinsb
Labels
area/documentation area/security lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone
1.5.1

Comments

@ProTip
Copy link

ProTip commented Aug 1, 2016

I'm aware that there are a few different kubernetes authentication options such as basic auth, client certificate, and tokens. It's not clear to me which is setup by kops.
@justinsb justinsb added this to the 1.3.0 milestone Aug 3, 2016
justinsb added a commit to justinsb/kops that referenced this issue Aug 15, 2016
@justinsb
Start work on documenting authentication/security
399e622 
In particular SSH

Issue kubernetes#166
Issue kubernetes#263
Issue kubernetes#236
@justinsb justinsb mentioned this issue Aug 15, 2016
Merged
@chrislovecnm
Copy link
Contributor

There is also an open issue for creating profiles.

@justinsb justinsb modified the milestones: 1.4.4, 1.5.0 Dec 28, 2016
@fejta-bot
Copy link

Issues go stale after 30d 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 19, 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 18, 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
Assignees

@justinsb justinsb

Labels
area/documentation area/security lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Milestone
1.5.1
Development

No branches or pull requests
5 participants
@justinsb @ProTip @chrislovecnm @k8s-ci-robot @fejta-bot