Feature Request: Add Support for priorityClassName in Forecastle Deployment

[andruwa13]

Description

Currently, Forecastle lacks the ability to specify a priorityClassName for its deployment, which limits its flexibility in Kubernetes cluster scheduling and resource management.

Motivation

• Enabling priorityClassName support allows for more granular control over pod scheduling
• Helps in implementing advanced resource allocation strategies
• Aligns with Kubernetes best practices for workload prioritization

Proposed Solution

Add a new configuration option to specify priorityClassName in the Forecastle deployment helm chart.

Detailed Implementation

• Update deployment template to include priorityClassName field
• Add corresponding configuration parameter in values.yaml (for Helm charts)
• Ensure backwards compatibility with existing deployments
• Add documentation for the new configuration option

Example Configuration

deployment:
  priorityClassName: high-priority