Currently to be able to use the cluster you need to ssh into a node within the master pool and extract the /etc/kubernetes/admin.conf file. This is currently a manual process to extract and requires:
It would be helpful if keto could expose a command to generate the config locally when provided with a cluster name and assets directory. The config should include the server address (AWS ELB), CA, client cert and key (required for kubectl to comm with the cluster). This would also greatly simplify automated end-to-end test steps.
Currently to be able to use the cluster you need to ssh into a node within the master pool and extract the
/etc/kubernetes/admin.conffile. This is currently a manual process to extract and requires:It would be helpful if keto could expose a command to generate the config locally when provided with a cluster name and assets directory. The config should include the server address (AWS ELB), CA, client cert and key (required for kubectl to comm with the cluster). This would also greatly simplify automated end-to-end test steps.