Feat/appel persistance

[AbdBoutchichi]

This pull request introduces a new Helm chart for deploying SmartDish microservices, including comprehensive Kubernetes manifests and environment-specific configuration files. The changes provide a standardized and flexible deployment setup for multiple services (API and SQLAPI) across integration and production environments, supporting best practices in configuration management, resource allocation, and security.

Helm Chart Structure and Templates:

• Added a new Helm chart directory with core files: Chart.yaml for chart metadata, _helpers.tpl for reusable template functions, and Kubernetes manifests for deployment, service, ingress, configmap, service account, and autoscaling (HPA). These templates enable scalable, maintainable, and environment-aware deployments. [1] [2] [3] [4] [5] [6] [7] [8]

Environment-Specific Configuration:

• Added distinct values files for API and SQLAPI services in both integration and production environments (values-api-integration.yaml, values-api-production.yaml, values-sqlapi-integration.yaml, values-sqlapi-production.yaml). These files define replica counts, resource limits, ingress settings, vault integration, health checks, and other service-specific parameters for each environment. [1] [2] [3] [4]

Default Configuration:

• Introduced a default values file (values.yaml) for the microservice chart, specifying baseline settings for replica count, image, service, ingress, autoscaling, vault, health checks, security context, and deployment strategy. This serves as a template for new microservices.

File Handling and Standards:

• Added a .gitattributes file to enforce consistent line endings and file handling for different file types, ensuring cross-platform compatibility and proper treatment of binary files.

Security and Best Practices:

• Incorporated security contexts, pod security contexts, and service account management in both templates and values files, following Kubernetes best practices for running containers with least privilege and managing access. [1] [2] [3] [4] [5] [6]

Let me know if you need more details on any specific part of the chart or configuration!