Generally follow the script from the end to end team.
Ensure you are running the traffic generator from Step 11.
- Pet Clinic App: Introduce the application.
- Github Source Code: Make an edit to the app and commit, trigging pipeline.
- Concourse Pipeline (petclinic pipeline): Show the pipeline and review the steps in the
c
ontinuous-integrationjob. Move onto following steps, but come back after a time to show that the
continuous-deployment` job is executing, and describe those steps. Including the event push to Tanzu Observability. - Harbor (Spring Pet Clinic Project): Show comment in the drop of vulnerabilities in the second image. Drill down into the vulnerabilities and show the project configuration preventing pulls.
- Kubeapps (petclinic namespace): Show the catalog, show the details of the deployed mysql db that serves petclinic.
- Octant (petclinic namespace): Show the application tab to give indications of the developer experience, check out the pod level information as well, like logs or exec into container.
- Tanzu Observability (Pet Clinic Custom Dashboard): Show the customized dashboard. Check out the event that now appears on in the charts. Don't forget to set the
Show Events
setting toFrom Dashboard Settings
. - Tanzu Mission Control: Show the workload cluster, highlight visibility into workloads, show data protection, and then link into Tanzu Observability to show cluster level metrics.
- Tanzu Application Catalog (MySql Helm Details): Discuss how the selection of apps in Kubeapps was curated and how you have visibility into security, functional, and license scans.
At this point the pipeline should be complete you and can check out updated spring pet clinic application.