User Details
- User Since
- Aug 19 2015, 9:13 PM (564 w, 1 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Etune [ Global Accounts ]
Sep 9 2015
Are you seeing that fatal log message in the apiserver log file?
you probably have a users[i].user.password and a users[i].user.token in that file.
You probably need to edit your .kube/config
You are setting " --insecure-bind-address=<%= @master_ip %> ".
unless master_ip is 127.0.0.1, that's probably not doing what you want.
Insecure port is likely reason for this.
Aug 27 2015
Ca you say a little bit more about what a "tool" is, or point to docs, so I can make sure I understand your use case.
Aug 26 2015
Some thoughts about service accounts and security contexts:
One simple thing that could work right now for you for authentication is to generate a password or a token per user, and put it in a file in each users directory, and also put that same credential in the APIserver's password and/or token file. And have some periodic process to add new ones for new users.
Aug 19 2015
Hi, I work on Kubernetes, and I'm new to the wikimedia environment. I see your requirement for "Proper user authentication / authorization that can tie into our existing system." Where could I find out how your existing system works, so I can perhaps work on a solution for you.