# Getting Started

## Prerequisites

- Kubernetes cluster (Kind for local development)
- Helm 3.x
- kubectl configured
- MySQL database available

## Local Development

### 1. Clone the repository

```bash
git clone https://gitea.os-tf-qa.onlinesales.ai/gitea_admin/schedulerService-chart.git
cd schedulerService-chart
```

### 2. Update Helm dependencies

```bash
helm dependency update helm/schedulerservice
```

### 3. Install with Helm (Local)

```bash
helm install scheduler-service helm/schedulerservice \
  -f helm/schedulerservice/values-local.yaml \
  -n scheduler \
  --create-namespace
```

### 4. Access the service

The service will be available at:
- http://schedulerservice.cnoe.localtest.me/schedulerService/

### 5. Verify health

```bash
curl "http://schedulerservice.cnoe.localtest.me/schedulerService/jobTrigger?jsonQuery=%7B%22application%22%3A%22nagios%22%2C%22jobName%22%3A%22monitoring_scheduler_svc%22%7D"
```

## Production Deployment

```bash
helm install scheduler-service helm/schedulerservice \
  -f helm/schedulerservice/values.yaml \
  -n scheduler \
  --create-namespace
```

## Database Setup

The service requires a MySQL database. The schema will be managed via Hibernate ORM.

### Local MySQL

When using `values-local.yaml`, a MySQL instance is deployed as a subchart with:
- Database: `os_scheduling_db`
- User: `scheduler_user`
- Password: `localpassword`