Den, I’m a fan limiting interactions with the cluster using specific roles and users to help with auditing purposes. A strategy I would recommend in your case would be to create users that have the specific permissions they need, and with a password they control. This will prevent your need to copy this configuration around everywhere.
-- John Skarbek On December 13, 2016 at 07:44:41, Den Cowboy ([email protected]<mailto:[email protected]>) wrote: Hi, I've installed openshift 1.3.2 for the first time with atomic as OS. It went fine. I used one normal centos as installation-server (so there ansible was installed and I executed the playbook there). Now is my question. What is the best way to interact with my environment. I've installed the oc-client tools on the centos server and I use ./oc login https://192.xx.xx.xx:8443<https://urldefense.proofpoint.com/v2/url?u=https-3A__192.xx.xx.xx-3A8443&d=DgMFAw&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=-3ai5GrWechgyR8zg7hEFYtEW2HyFmlflRdhGicSQek&s=oi-HEtx5WpeimPBC0C0sR5fhH387nVzVgIHUtmoyrQQ&e=> to authenticate. But when I want to authenticate as system:admin I need the $KUBECONFIG (admin.kubeconfig). Is it a normal approach to copy this file from my os-master (atomic) to my centos server from which I try to manage everything? Or do I need to install the client tools on my master itself? What is the most common approach? Thanks _______________________________________________ users mailing list [email protected] https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=DgICAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=8IlWeJZqFtf8Tvx1PDV9NsLfM_M0oNfzEXXNp-tpx74&m=-3ai5GrWechgyR8zg7hEFYtEW2HyFmlflRdhGicSQek&s=DtLlLgc3iRNtUzHSjKdoFWsKFQSQWH9d0149B4yvhO4&e=
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
