The reverse proxy's transport was nil when using the ambient kube config. This led to panics. This corrects the transport when using the ambient kube config.
Modified dev:up so it copies over all certs in case we want to test with a client running outside of the kind cluster.
in case multiple SpiceDB tokens are passed, separated by commas, the proxy now picks the first token of the list. This helps when mounting the secret from an external SpiceDB that defines multiple tokens.
fix options validation so that it does not require --backend-kubeconfig when --use-in-cluster-config is present
nilwhen using the ambient kube config. This led to panics. This corrects the transport when using the ambient kube config.dev:upso it copies over all certs in case we want to test with a client running outside of the kind cluster.--backend-kubeconfigwhen--use-in-cluster-configis present