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:41:16+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 Spring Boot application deployed via ArgoCD into the demo-apps namespace, featuring OpenTelemetry instrumentation and support for load testing and chaos engineering.

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 building modern Java applications. This service is scaffolded using the Backstage Application Migration Factory template and integrates observability, load testing, and chaos engineering capabilities.

The application provides a web interface for managing veterinary clinics, including features for scheduling appointments, managing pet records, and handling customer information. It is deployed in the demo-apps namespace and continuously synced via ArgoCD from the main branch of its source repository. OpenTelemetry instrumentation is enabled for comprehensive observability, and the service supports load testing using K6 and chaos engineering experiments via Chaos Mesh.

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 service is based on the Spring PetClinic application, cloned from https://github.com/spring-projects/spring-petclinic.
• OpenTelemetry auto-instrumentation is applied via Kustomize overlays, enabling detailed tracing, metrics, and logging.
• ArgoCD manages the deployment, continuously syncing changes from the main branch to the demo-apps namespace.
• The application supports multiple database configurations, including H2 (default), MySQL, and PostgreSQL, with profiles for each.

Configuration

Configuration	Description
spring.profiles.active	Sets the active Spring profile (mysql, postgres, or default h2).
Database URLs	H2: jdbc:h2:mem:<uuid> (default), MySQL: docker-compose.yml service mysql, PostgreSQL: docker-compose.yml service postgres.
OpenTelemetry Collector	Endpoint: http://otel-collector.monitoring.svc.cluster.local:4318.

Operations

• Development Workflow:

  git clone https://gitea.kyndemo.live/validate/petclinic-demo-jonathan-scaf-2.git
  cd petclinic-demo-jonathan-scaf-2
  # make changes, then:
  git add . && git commit -m "your change" && git push origin main
  

  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
• Alerting: Configured via Grafana with label selector app.kubernetes.io/instance=petclinic-demo-jonathan-scaf-2.
• Instrumentation: OpenTelemetry traces, metrics, and logs exported to the OTel Collector.

Dependencies

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