platform-docs/catalog/component/default/petclinic-demo-jonathan-scaf-2/README.md

title, generated_by, generated_at, human_edited, source_entity, source_repo

title	generated_by	generated_at	human_edited	source_entity	source_repo
Petclinic Demo Jonathan Scaf 2	documentor-agent	2026-05-05T10:49:39+00:00	false	Component/default/petclinic-demo-jonathan-scaf-2	https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2

Petclinic Demo Jonathan Scaf 2

A deployment of the Spring PetClinic application, scaffolded via Backstage and integrated with OpenTelemetry, ArgoCD, and Chaos Mesh.

Overview

Petclinic Demo Jonathan Scaf 2 is a deployment of the Spring PetClinic application, a sample Spring Boot project designed to showcase best practices in Java application development. This deployment integrates modern DevOps tools and practices, including ArgoCD for continuous delivery, OpenTelemetry for observability, and Chaos Mesh for chaos engineering experiments.

The application provides a web interface for managing veterinary clinics, including features for scheduling appointments, managing pet records, and tracking veterinary staff. It is deployed in the demo-apps namespace and continuously synced from the main branch of its source repository. Observability is enabled via OpenTelemetry, with metrics and traces visualized in Grafana.

Repository

Field	Value
Source Repo	https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2
Branch	main
ArgoCD App	petclinic-demo-jonathan-scaf-2
Namespace	demo-apps

Architecture

• The application is based on the Spring PetClinic project, cloned from https://github.com/spring-projects/spring-petclinic.
• OpenTelemetry auto-instrumentation is applied via Kustomize overlays, enabling detailed observability.
• ArgoCD manages the deployment, continuously syncing changes from the main branch to the demo-apps namespace.
• Chaos Mesh is enabled for chaos engineering experiments, allowing resilience testing of the application.

Deployment flow:

1. Source code is cloned and scaffolded using Backstage templates.
2. OpenTelemetry instrumentation is injected.
3. ArgoCD syncs the application from the repository to the Kubernetes cluster.

Configuration

Configuration	Description
Environment Variables	spring.profiles.active for database configuration (mysql, postgres, or default for H2).
Database	Default is H2; supports MySQL and PostgreSQL with Docker or Docker Compose.
Observability	OpenTelemetry endpoint: http://otel-collector.monitoring.svc.cluster.local:4318.

Operations

Deployment Workflow

1. Clone the repository:

   git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git
   cd petclinic-demo-jonathan-scaf-2
   

2. Make changes and push:

   git add . && git commit -m "your change" && git push origin main
   

3. ArgoCD automatically syncs changes to the demo-apps namespace.

Rollback

1. Open the ArgoCD UI.
2. Click History and Rollback.
3. Select the desired revision and click Rollback.

Alternatively, revert the commit in Git and push — ArgoCD will auto-sync the rollback.

Observability

• Grafana Dashboard: https://grafana.kyndemo.live/d/otel-app-observability-v2/opentelemetry-application-observability?orgId=1&var-app=petclinic-demo-jonathan-scaf-2
• OpenTelemetry instrumentation is enabled, exporting traces, metrics, and logs to the OTel Collector.

Not configured — see platform observability docs.

Dependencies

• component:default/argocd-service
• resource:default/k6-operator
• resource:default/otel-collector
• resource:default/veterinary-platform