An "init" command to integrate Arlon with ArgoCD, and optionally create a "starter kit" of example bundles, profiles, clusterspecs, baseclusters?

[bcle]

Arlon setup is still very complex, in particular in these areas:

• Authentication integration with argocd
• The need to create a bunch of bundles, profiles, clusterspecs, base clusters (when using next-gen clusters) before anything useful can be done

Aha! Link: https://pf9.aha.io/features/ARLON-298

[Rohitrajak1807]

@bcle is the auth integration with argocd the same as doing these steps from Arlon installation:

Follow steps 1-4 of the ArgoCD installation guide to install ? ArgoCD onto your management cluster. After this step, you should be logged in as admin and a config file was created at > ${HOME}/.config/argocd/config Create your workspace repository in your git provider if necessary, then register it. Example: argocd repo add https://github.com/myname/arlon_workspace --username myname --password secret. Note: type argocd repo add --help to see all available options. For Arlon developers, this is not your fork of the Arlon source code repository, but a separate git repo where some artifacts like profiles created by Arlon will be stored. Highly recommended: configure a webhook to immediately notify ArgoCD of changes to the repo. This will be especially useful during the tutorial. Without a webhook, repo changes may take up to 3 minutes to be detected, delaying cluster configuration updates. Create a local user named arlon with the apiKey capability. This involves editing the argocd-cm ConfigMap using kubectl. Adjust the RBAC settings to grant admin permissions to the arlon user. This involves editing the argocd-rbac-cm ConfigMap to add the entry g, arlon, role:admin under the policy.csv section. Example: apiVersion: v1 data: policy.csv: | g, arlon, role:admin kind: ConfigMap [...] Generate an account token: argocd account generate-token --account arlon Make a temporary copy of the config file: cp ${HOME}/.config/argocd/config /tmp/config then edit it to replace the value of auth-token with the token from the previous step. Save changes. This file will be used to configure the Arlon controller's ArgoCD credentials during the next steps.

[bcle]

Yes, more or less. We need some form of quick start. Some steps could be made optional, depending on what the user already has. For e.g. if they already have ArgoCD in the management cluster, then integrate with it. Otherwise, offer to install it, similar to the testbed script.

[Rohitrajak1807]

Integrating arlon with argocd seems to be quite involved and has many steps. Readjusting estimate to size Large.

[Rohitrajak1807]

@bcle when you say:

... create a "starter kit" of example bundles, profiles, clusterspecs, baseclusters?

Do you mean just push dummy basecluster manifests or do we have to run the clusterawsadm command, then install CAPI and then generate the manifest and finally push it?