Providing the Git private SSH key via its filepath is not GitOps friendly

[marccarre]

Problem

Currently, we accept --git-private-ssh-key-path and will soon have the equivalent in ClusterConfig. However, this will not work well with a cluster-level GitOps approach, as the file path only is meaningful for the local machine.

Solution

Instead, we should refer a key in a Kubernetes Secret or in AWS, e.g.:

1. register the SSH key in AWS:

   eksctl create keypair $keyName --from-file /path/to/private/ssh/key/file/id_rsa

2. run eksctl enable repo the following way:

   eksctl enable repo --git-private-ssh-key-name $keyName

   or

   eksctl enable repo -f /path/to/clusterconfig.yaml

   having $keyName present in there.

See also #1211, #1273

[Callisto13]

Closing due to #2963