Upgrade Kubernetes version to 1.35 in AWS cluster configs

[jkroll-deepgram]

Proposed changes

Upgrade Kubernetes version from 1.33 to 1.35 in AWS cluster configs ahead of end-of-support.

See AWS EKS doc: Understand the Kubernetes version lifecycle on EKS

Kubernetes 1.33 (Deepgram chart's prior version):

• Standard support ends July 29, 2026 [in less than 3 months]
• Extended support ends July 29, 2027

Kubernetes 1.35 (Deepgram chart's new version):

• Standard support ends March 27, 2027
• Extended support ends March 27, 2028

I tested in EKS and it works as expected, no issues updating a Deepgram cluster from 1.33 to 1.35 and serving requests.

Types of changes

What types of changes does your code introduce to the Deepgram self-hosted resources?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have tested my changes in my local self-hosted environment
  • Please describe your testing setup and methodology here
• I have added necessary documentation (if appropriate)

Further comments