The most important ingredient using eksctl enable repo is the configuration of your repository (which will include your workload manifests, HelmReleases, etc). You can start with an empty repository and push that to Git, or use the one you intend to deploy to the cluster.

The main point of GitOps is to keep everything (config, alerts, dashboards, apps, literally everything) in Git and use it as a single source of truth. To keep your cluster configuration in Git, please go ahead and create an empty repository. On GitHub, for example, follow these steps..

In the Cloud9 environment, a user SSH key pair is not automatically created. Use these instructions to create an SSH key pair for use as your git repository deploy keys.

Open a new terminal in your Cloud9 workspace and run the following commands.

To create a new ssh key, run the following. Substitute your github email address where specified.

ssh-keygen -t rsa -b 4096 -C ""

Start the ssh-agent in the background.

eval "$(ssh-agent -s)"

Add your SSH private key to the ssh-agent and store your passphrase in the keychain. If you created your key with a different name, or if you are adding an existing key that has a different name, replace id_rsa in the command with the name of your private key file.

ssh-add ~/.ssh/id_rsa

Then run:

cat ~/.ssh/

You can then create a deploy key in your repository by going to: Settings > Deploy keys. Click on Add deploy key, and check Allow write access. Then paste your public key and click Add key. This will allow us to clone this repo to our Cloud9 environment. Instructions to do so are here.