<p>I'm am currently configuring Heketi Server (Deployed on K8S clusterA) to interact with my Glusterfs cluster that is deployed as a DaemonSet on another K8S cluster ClusterB.</p>

<p>One of the configurations required by Heketi to connect to GlusterFS K8S cluster are :</p>

<pre><code>    "kubeexec": {
      "host" :"https://&lt;URL-OF-CLUSTER-WITH-GLUSTERFS&gt;:6443",
      "cert" : "&lt;CERTIFICATE-OF-CLUSTER-WITH-GLUSTERFS&gt;",
      "insecure": false,
      "user": "WHERE_DO_I_GET_THIS_FROM",
      "password": "&lt;WHERE_DO_I_GET_THIS_FROM&gt;",
      "namespace": "default",
      "backup_lvm_metadata": false
    },
</code></pre>

<p>As you can see, it requires a user and password. I have no idea where to get that from. 
One thing that comes to mind is creating a service account on ClusterB and using the token to authenticate but Heketi does not seem to be taking that as an authentication mechanism. </p>

<p>The cert is something that I got from <code>/usr/local/share/ca-certificates/kube-ca.crt</code> but I have no idea where to get the user/password from. Any idea what could be done?</p>

<p>If I do a <code>kubectl config view</code> I only see certificates for the admin user of my cluster.</p>

<p>That could only mean one thing: <a href="https://kubernetes.io/docs/reference/access-authn-authz/authentication/#static-password-file" rel="nofollow noreferrer">basic HTTP auth</a>.</p>

<p>You can specify a username/password in a file when you start the kube-apiserver with the <code>--basic-auth-file=SOMEFILE</code> option.</p>
