An Example for Reference implementation lite

[nabuskey]

The reference implementation being worked on is too heavy. We need a lite version where only the essential components with no security configuration. This is likely more suitable for development purposes.

Possible Components:

• Backstage
• Crossplane
• Argo Workflows

[nimakaviani]

do you need cert-manager and keycloak as part of this?

[cmoulliard]

From my point of view, we need:

• Backstage
• ArgoCD
• CertManager
• Tekton (optional) => only if we would like to propose some templates for IDP able to streamline the build, test and deployment process using Pipelines (build, test) and Helm chart for the deployment. Remark: ArgoCD will be used here as App of Apps and will deploy using a parent App the children Applications able to build, test, etc
• Keycloak (optional): it implies also that you configure kubectl to use OIDC to authenticate the user against the platform and to patch the kind config when we install it. Example about what to do is available here: https://github.com/snowdrop/kube-oidc-keycloak

Remarks: Ideally our idp apps should include natively the following plugins: argocd, tekton, keycloak & kubernetes with cluster-admin role. Example: https://github.com/q-shift/backstage-playground

[nimakaviani]

Please feel free to check and provide feedback on this PR @cmoulliard https://github.com/cnoe-io/idpbuilder/pull/138

we have:

• Backstage
• ArgoCD
• Nginx
• Keycloack
• Argo Workflows
• Crossplane
• Terraform Provider

Tekton and Argo Workflows are interchangeable of course and Keycloak is configured to allow SSO across all tools.

[nabuskey]

do you need cert-manager and keycloak as part of this?

I don't think I want to have these. I want this to be light and be easily used together with IDEs for development purposes. We can probably lose Crossplane too.

I am thinking:

• Backstage with no auth
• Argo Workflows with no auth