Configure api.kernelci.org in Kubernetes Production Cluster

## Background
The api.kernelci.org domain is now available for use following the legacy system decommissioning. The DNS records have been updated to point to our production cluster.

## Task
Configure the api.kernelci.org domain within the Kubernetes cluster to enable proper routing and service discovery, and letsencrypt

## Current Status
- DNS records are properly configured at the infrastructure level
- Domain points to production cluster
- Kubernetes configuration pending

## Required Actions
1. Update Kubernetes ingress configuration to handle api.kernelci.org traffic
2. Configure TLS certificates for secure communication
3. Verify routing rules and service mappings
4. Test domain accessibility and functionality

## Expected Outcome
The api.kernelci.org domain should be fully operational within the Kubernetes cluster, handling API requests securely and efficiently.

Start by locating the production Kubernetes ingress manifests and the existing TLS or Let's Encrypt configuration; the issue does not name specific files or tests. Trace the current service mappings and routing rules for the production cluster. Done means api.kernelci.org routes to the API, has a valid TLS certificate, and its accessibility and functionality have been verified.

Scritto dal modello di indicizzazione a partire dal testo della issue.