title: How to use etcdctl without supplying certificates
body: <p>Heey All,</p>
  
  <p>Maybe a very stupid question but I've got a CoreOS cluster with SSL between the cluster nodes. I've set up fleet and etcd within my cloud config.</p>
  
  <p>fleetctl works quite nice. I don't have to supply any certificates but when I use etcdctl I'm forced supply certificate paths like this:</p>
  
  <pre><code>etcdctl --ca-file /home/core/etcd/certificates/ca.pem --cert-file /home/core/etcd/certificates/coreos.pem --key-file /home/core/etcd/certificates/coreos-key.pem --endpoint "https://10.129.1.226:2379" get /test/key
  </code></pre>
  
  <p>Is there a way that etcd2 can be configured in such a way that etcdctl doesn't need the certificate paths every time like:</p>
  
  <pre><code>etcdctl get /test/key
  </code></pre>
  
  <p>Part of my Cloud config:</p>
  
  <pre><code>write_files:
    # tell etcd2 and fleet where our certificates are going to live:
    - path: /run/systemd/system/etcd2.service.d/30-certificates.conf
      permissions: 0644
      content: |
        [Service]
        # client environment variables
        Environment=ETCD_CA_FILE=/home/core/etcd/certificates/ca.pem
        Environment=ETCD_CERT_FILE=/home/core/etcd/certificates/coreos.pem
        Environment=ETCD_KEY_FILE=/home/core/etcd/certificates/coreos-key.pem
        # peer environment variables
        Environment=ETCD_PEER_CA_FILE=/home/core/etcd/certificates/ca.pem
        Environment=ETCD_PEER_CERT_FILE=/home/core/etcd/certificates/coreos.pem
        Environment=ETCD_PEER_KEY_FILE=/home/core/etcd/certificates/coreos-key.pem
  </code></pre>