Enable Configurable TLS and Auth for Non-Production Environments

[ckaytev]

This is a cool project! I hope the community appreciates it.

I encountered some issues while setting up runtime-radar in a non-production environment with TLS disabled.
This PR simplifies the process by making TLS and authentication settings more flexible. Here’s what’s included:

What’s Fixed

1. Added global.tls.enabled and global.auth.enabled (default: true). This lets us disable security features in dev or staging without changing the code.

2. Reverse-Proxy no longer requires certificates. Previously, even with TLS disabled, the reverse-proxy still needed certificates. Now, the Helm chart explicitly sets TLS=false in environment variables when disabled, so there are no more "missing certs" errors.

3. No unnecessary token generation. When authentication is disabled (global.auth.enabled=false), the chart no longer creates random tokens or adds unused annotations. This reduces unnecessary outputs and keeps the setup clean.

Why This Helps

These changes make it easier to deploy runtime-radar in non-production environments. With TLS and auth turned off, the system works smoothly without extra configuration.

How to Test

1. Set global.tls.enabled=false and global.auth.enabled=false in values.yaml.
2. Deploy the chart and verify:
   • the reverse-proxy starts without TLS errors
   • no extra tokens or secrets are created
   • components connect without "grpc: the credentials require transport level security" errors

Let me know if you want any changes. I am happy to make adjustments.
P.S. The changes are mostly adding conditionals and documentation. There are no breaking changes.

[nikiladonya]

@ckaytev hello! We will review soon your PR, thx!