# Kubernetes Infrastructure Review with Turf Dev

> A free 30-minute call with Turf Dev’s Kubernetes team. You walk us through your setup, and we tell you what we’d fix first. We’ll cover: Your clusters, cloud and CI/CD setup today The biggest risks we see: security gaps, reliability, cost What’s driving this now: a compliance review, a migration, a new platform, or on-call load A recommended next step, with scope and a price range, if there’s a fit Good for teams on EKS, AKS, GKE or self-managed Kubernetes, or planning a move to it. No slides and no hard sell. If you can, have an architecture diagram or a rough list of services handy.

- Host: Turf Dev
- Duration: 30 min
- Location: Cal Video, Zoom Video
- Host time zone: Asia/Calcutta
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/turf-dev/infrastructure-audit
- Event type id: 7911415

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=7911415&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 7911415,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "Current-Infrastructure-Setup": "…",
    "Primary-Challenge": "…",
    "Engineering-Team-Size": "…",
    "attendeePhoneNumber": "…",
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address), `Current-Infrastructure-Setup` (Current Infrastructure Setup), `Primary-Challenge` (Primary Challenge), `Engineering-Team-Size` (Engineering Team Size)
- Optional fields: `attendeePhoneNumber` (Phone number), `notes` (Additional notes), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
- `location` is optional; without it the booking uses the event’s first location.