IDP installation flow
The idpbuilder cli installs a local internal developer portal using the following pattern:
- Create a new Kind cluster if one doesn't exist or if
--recreateswitch is passed.
- Install Gitea available at https://gitea.cnoe.localtest.me:8443
- Install ArgoCD and configure it to be able to monitor applications from the Gitea service, available at https://argocd.cnoe.localtest.me:8443
- Install Nginx for ingress traffic management.
- Argo apps for ArgoCD, Gitea, and Nginx ingress are reconciled by ArgoCD.
- Command line exits leaving the cluster running with the IDP stack installed.
The tool also comes with the option to install the CNOE recommended IDP stack:
- Backstage becomes available on your localhost via an Nginx ingress at https://backstage.cnoe.localtest.me:8443
- Keycloak becomes available on your localhost via an Nginx ingress at https://keycloak.cnoe.localtest.me:8443
- Crossplane becomes available on your localhost, managing Crossplane resources deployed to the Kind cluster
Use kubectl to get the correct IDP address/hostname to connect to.
- Docker must be installed and available to the current user.
- Internal Developer Portal components are installed as ArgoCD Applications.
- The ArgoCD apps that are installed are embedded in the cli binary. See cnoe-io/idpbuilder/pkg/controllers/localbuild/controller.go