Kops: Option to turn off basic auth

Created on 10 Aug 2016 · 15Comments · Source: kubernetes/kops

This may be as simple as _not_ passing basic-auth-file to the api server, but need to understand what else this disables!

aresecurity lifecyclrotten

Source

justinsb

👍13

Most helpful comment

I am super keen to see this happen.

jurgenweber on 21 Feb 2018

👍18

All 15 comments

Thanks for adding this issue. For what it's worth, our fork that completely removes basic auth is working well for us. Obviously this isn't a great solution for the main project as many people actually will want basic auth enabled.

robscott on 10 Aug 2016

@robscott are you interesting in helping move support into main?

chrislovecnm on 27 Oct 2016

We do have the flag mapped in 1.5.0, so I would close, but I hope to look more at the fork (thanks @robscott) as we look at making auth easier to use. Moving to 1.5.1

justinsb on 30 Jan 2017

@justinsb My fork is really nothing much other than just removing basic auth entirely. It was rather hacky so probably not worth looking at. I'm glad this option has made it into the main project, I'm really looking forward to upgrading to 1.5. What flag do I need to use to disable basic auth?

robscott on 30 Jan 2017

Is this fixed?

chrislovecnm on 29 Apr 2017

any news on how to do this?

jurgenweber on 23 Nov 2017

Not implemented as of yet

chrislovecnm on 23 Nov 2017

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.

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

fejta-bot on 21 Feb 2018

/remove-lifecycle stale

jurgenweber on 21 Feb 2018

I am super keen to see this happen.

jurgenweber on 21 Feb 2018

👍18

https://github.com/kubernetes/kops/pull/4799 should fix this.

valdisrigdon on 17 Apr 2018

🎉1

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.

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

fejta-bot on 16 Jul 2018

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

fejta-bot on 16 Aug 2018

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

fejta-bot on 15 Sep 2018

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.