Turn local configuration into cluster resources

`stack.sh` defaults to a local kubeconfig path, installs KEDA if its custom resource definition is missing, creates the application namespace, generates a `secrets.env` file if needed, creates a Kubernetes Secret, and applies `manifests/stack.yaml`. A separate `check` command waits for pods to become ready; `status` and `url` expose narrower operational checks.

The generated file uses random values and mode 600, and `.gitignore` excludes the secret file. Regenerating a database password after the PostgreSQL volume already exists can desynchronize the Kubernetes Secret from the password initialized in the database, so the script warns about that stateful consequence.

export KUBECONFIG=/secure/path/to/config.yml
./stack.sh up
./stack.sh check
./stack.sh url

A Secret object is not a complete secrets system

The application password, database URL, UI signing key, and Grafana password are passed to pods through Kubernetes Secret references. This keeps values out of the main workload manifest, but it does not by itself provide secret rotation, external key management, or encrypted backups. The project’s production notes point to managed secret solutions for that next step.

There is a small reproducibility and hygiene mismatch: both shell wrappers default to `config.yml`, while `.gitignore` names `config.yaml`. Use a kubeconfig stored outside the repository or align the ignore rule before placing credentials in the project directory.

Keep privileged tools and public access constrained

The chat interface is the only LoadBalancer, and the demo uses plain HTTP without an ingress controller or OIDC configuration. The first registered Open WebUI user becomes an administrator. A public deployment therefore needs deliberate identity, transport security, abuse controls, and a decision about who may create accounts.

`dash.sh` exposes the Kubernetes Dashboard only through a local port-forward, but `manifests/dash.yaml` binds its service account to `cluster-admin`. The helper creates a time-limited token; that convenience still carries cluster-wide authority. The README labels this setup demo-only. Do not expose the dashboard publicly or reuse this permission model for a shared cluster.