Option to turn off basic auth

[justinsb]

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

[robscott]

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.

[chrislovecnm]

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

[justinsb]

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

[robscott]

@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?

[chrislovecnm]

Is this fixed?

[jurgenweber]

any news on how to do this?

[chrislovecnm]

Not implemented as of yet

[fejta-bot]

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

[jurgenweber]

/remove-lifecycle stale

[jurgenweber]

I am super keen to see this happen.

[valdisrigdon]

#4799 should fix this.

[fejta-bot]

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]

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]

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

[k8s-ci-robot]

@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.