Support for SSL with internal etcd

[asusk7m550]

Describe the Bug

When a new setup is created with manage_etcd is false, the puppet module will use kubeadm to setup a new etcd cluster with SSL. But it will not copy the SSL certificates in the correct path.

Expected Behavior

The SSL certificates which are defined, will be placed in the correct path.

Steps to Reproduce

Steps to reproduce the behavior:

class {'kubernetes':
  controller => true,
  
  # Certificate settings
  etcd_ca_key                       => "<etcd_ca_key>",
  etcd_ca_crt                       => "<etcd_ca_crt>",
  etcdclient_key                    => "<etcdclient_key>",
  etcdclient_crt                    => "<etcdclient_crt>",
  etcdserver_key                    => "<etcdserver_key>",
  etcdserver_crt                    => "<etcdserver_crt>",
  etcdpeer_key                      => "<etcdpeer_key>",
  etcdpeer_crt                      => "<etcdpeer_crt>",
  kubernetes_ca_key                 => "<kubernetes_ca_key>",
  kubernetes_ca_crt                 => "<kubernetes_ca_crt>",
  kubernetes_front_proxy_ca_crt     => "<kubernetes_front_proxy_ca_crt>",
  kubernetes_front_proxy_ca_key     => "<kubernetes_front_proxy_ca_key>",
  sa_pub                            => "<sa_pub>",
  sa_key                            => "<sa_key>",

  # ETCd settings
  manage_etcd                       => false,
  etcd_ip                           => $facts['networking']['ip'],
  etcd_peers                        => ['192.168.2.1', '192.168.2.2', '192.168.2.3'],
  etcd_initial_cluster              => "k8s-master01=https://192.168.2.1:2380,k8s-master02=https://192.168.2.2:2380,k8s-master03=https://192.168.2.3:2380"
}

Environment

• Version: all versions
• Platform: all platforms

Additional Context