Folks,
I've set up Cockpit/Kubernetes on a new atomic cluster, but I can't log into it. I've tried both the standard password, and various system users, and can't log in.
Where is it getting auth credentials from?
On 06/16/2016 10:59 AM, Josh Berkus wrote:
Folks,
I've set up Cockpit/Kubernetes on a new atomic cluster, but I can't log into it. I've tried both the standard password, and various system users, and can't log in.
Where is it getting auth credentials from?
What I've tried so far:
* setting insecure login to the whole network * adding --basic-auth-file
These didn't help.
On 06/16/2016 12:26 PM, Josh Berkus wrote:
On 06/16/2016 10:59 AM, Josh Berkus wrote:
Folks,
I've set up Cockpit/Kubernetes on a new atomic cluster, but I can't log into it. I've tried both the standard password, and various system users, and can't log in.
Where is it getting auth credentials from?
What I've tried so far:
- setting insecure login to the whole network
- adding --basic-auth-file
These didn't help.
When using the cockpit/kubernetes container you are logging in against the the kubernetes API server, so the credentials to use can be specified in your --basic_auth_file. You are also probably going to want at least ServiceAccount and NamespaceExists in your --admission-control settings.
On 06/16/2016 12:26 PM, Josh Berkus wrote:
On 06/16/2016 10:59 AM, Josh Berkus wrote:
Folks,
I've set up Cockpit/Kubernetes on a new atomic cluster, but I can't log into it. I've tried both the standard password, and various system users, and can't log in.
Where is it getting auth credentials from?
What I've tried so far:
- setting insecure login to the whole network
- adding --basic-auth-file
These didn't help.
When using the cockpit/kubernetes container you are logging in against the the kubernetes API server, so the credentials to use can be specified in your --basic_auth_file. You are also probably going to want at least ServiceAccount and NamespaceExists in your --admission-control settings.
cockpit-devel@lists.fedorahosted.org