Merge branch 'main' into feat/deploy

Resolve conflicts by keeping main branch changes for dev environment:
- Use updated README.md from main with dev environment clarifications
- Keep dev/values.yaml configurations from main
- Retain prod/values.yaml for production environment with proper prod settings

Signed-off-by: Tibor Kircsi <tkircsi@cisco.com>

Author: tkircsi

README.md

@@ -20,7 +20,12 @@ provided as-is for demonstration and testing purposes.
 To onboard a new environment to **Directory Public Staging Network**, check the
 [onboarding guide](onboarding/README.md).
 
-## Quick Start
+## Quick Start (Development Environment)
+
+> [!NOTE]
+> This guide sets up the **development environment** for local testing and development.
+> It uses a local Kind cluster with NodePort services and simplified security.
+> For production deployment with Ingress and TLS, see the [Production Setup](#production-setup) section below.
 
 This guide demonstrates how to set up AGNTCY Directory project using
 Argo CD in Kubernetes [Kind](https://kind.sigs.k8s.io/) cluster.
@@ -72,15 +77,15 @@ Verify deployment by checking the results of CronJobs in `dir-admin` application
 kind delete cluster --name dir-dev
 ```
 
-### Token-based Directory Client authentication
+### Token-based Directory Client Authentication (Dev)
 
 In some cases, you may want to use Directory Client locally
 without SPIRE stack.
 In this case, you can use token-based authentication
 using SPIFFE X509 SVID tokens.
 
 To generate a SPIFFE SVID token for authenticating local Directory Client
-with the Directory Server, follow these steps:
+with the Directory Server in the dev environment, follow these steps:
 
 1. Create a SPIFFE SVID for local Directory Client