hello-world and wordpress examples#1
Conversation
| name: kubeplus-wordpress-tenants | ||
| namespace: argocd | ||
| spec: | ||
| project: kubeplus-tenants |
There was a problem hiding this comment.
Change the project name to "wordpress-tenants"
| apiVersion: argoproj.io/v1alpha1 | ||
| kind: AppProject | ||
| metadata: | ||
| name: kubeplus-tenants |
There was a problem hiding this comment.
Change the name to "wordpress-tenants"
| apiVersion: argoproj.io/v1alpha1 | ||
| kind: AppProject | ||
| metadata: | ||
| name: kubeplus-tenants |
There was a problem hiding this comment.
Change the name to "helloworld-tenants"
| name: kubeplus-hello-world-consumer | ||
| namespace: argocd | ||
| spec: | ||
| project: kubeplus-tenants |
There was a problem hiding this comment.
helloworld-tenants
| name: kubeplus-hello-world-provider | ||
| namespace: argocd | ||
| spec: | ||
| project: kubeplus-provider |
There was a problem hiding this comment.
Change this to helloworld-provider
| apiVersion: argoproj.io/v1alpha1 | ||
| kind: AppProject | ||
| metadata: | ||
| name: kubeplus-provider |
There was a problem hiding this comment.
Change this to helloworld-provider
| git add multitenancy/application-hosting/hello-world-argocd/provider/hello-world-service-composition.yaml | ||
| git commit -m "Test hello world provider Argo CD sync" | ||
| git push | ||
| kubectl annotate application kubeplus-hello-world-provider -n argocd argocd.argoproj.io/refresh=hard --overwrite |
There was a problem hiding this comment.
Why do we have to annotate argocd application?
Add an explanation.
| name: kubeplus-wordpress-provider | ||
| namespace: argocd | ||
| spec: | ||
| project: kubeplus-provider |
There was a problem hiding this comment.
Change the project name to wordpress-provider
| apiVersion: argoproj.io/v1alpha1 | ||
| kind: AppProject | ||
| metadata: | ||
| name: kubeplus-provider |
There was a problem hiding this comment.
wordpress-provider
| git add multitenancy/application-hosting/wordpress-argocd/provider/wordpress-service-composition.yaml | ||
| git commit -m "Test wordpress provider Argo CD sync" | ||
| git push | ||
| kubectl annotate application kubeplus-wordpress-provider -n argocd argocd.argoproj.io/refresh=hard --overwrite |
There was a problem hiding this comment.
Add a comment as to why this step is added.
| - Tenant apps can sync as `kubeplus-saas-consumer`, which can create `GitopsWPService` instances but cannot create `ResourceComposition`. | ||
| - Both ArgoCD applications point at `cloud-ark/kubeplus-examples`, but | ||
| use different subpaths under `multitenancy/application-hosting/wordpress-argocd/`. | ||
| - The shorter custom kind `GitopsWPService` avoids KubePlus's Helm release-name length limit and allows tenant names like `wp-tenant1`. |
Added hello-world and wordpress provider/tenant gitops examples with ArgoCD