Projects Guide

[jeffmccune]

The second guide after the Quickstart. The theme is how Holos makes it easier for a platform team to provide a project structure for development teams.

Outline

Intended audience is a platform engineer.

• Goal is to show the reader how to manage a project for a dev team.
• The dev team wants to deploy a container onto the platform.
• [ ] Reader starts by forking a git repo that contains a basic platform.
• [ ] ArgoCD is accessible straight away.
• [ ] Exercise: Change the git url to point to the fork.
• [ ] Notice how all of the platform components change consistently to the new URL.
• [ ] Exercise: Create a new project. (Deployment, Service)
• [ ] Assume the dev team creates their own project from documentation. Use a super basic schematic as an example.
• [ ] Adding the project needs two platform resources: Namespace, HTTPRoute. Both go into /projects
• [ ] Adding the project needs needs to register the component. Registration goes into the rott /
• [ ] Notice how easy Holos makes it for the developers to update their image tag.

Bank of Holos

• [x] frontend
• [x] accounts-db
• [x] userservice
• [x] Fix ArgoCD SharedResourceWarnings
• [x] ledgerwriter service
• [x] balancereader service
• [x] transactionhistory service
• [x] contacts
• [x] Fix redirects to http causing connection reset errors. See https://github.com/GoogleCloudPlatform/bank-of-anthos/issues/478
• [ ] loadgenerator

Next Steps (Level 3)

This Level 2 guide should set the stage for the policy management theme.

• Block CRD's being added from certain projects.
• Discuss how resources can be limited or allowed.
• Discuss how labels can be applied.
• How Holos plays nicely with OWNERS.

Connections to Quickstart

• [ ] Update Quickstart guide to fork a different repo.
• [ ] Change the Quickstart to the same directory structure.

[jeffmccune]

Closing to focus on #251