miki3421 commented on issue #271:
URL: https://github.com/apache/openserverless/issues/271#issuecomment-6145083096

   Thanks for reporting this. The error suggests that `kubectl`, invoked by 
`ops config sso`, is not picking up a valid Kubernetes configuration. It is 
trying to reach `localhost:8080`, so the command fails while applying the SSO 
configuration, before we can assess the Keycloak integration.
   
   Could you run these checks in the same terminal, as the same user you use 
for `ops config sso`?
   
   ```bash
   printf 'KUBECONFIG=%s\n' "$KUBECONFIG"
   kubectl config current-context
   kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}'
   printf '\n'
   kubectl cluster-info
   ```
   
   An empty `KUBECONFIG` variable is not necessarily a problem: `kubectl` 
normally falls back to `~/.kube/config`.
   
   If your cluster configuration is stored elsewhere, point to the existing 
file explicitly:
   
   ```bash
   export KUBECONFIG=/path/to/your/kubeconfig
   kubectl cluster-info
   ```
   
   Once that command successfully connects to the intended cluster, retry `ops 
config sso keycloak` in the same terminal. The kubeconfig must provide 
sufficient permissions to apply the SSO configuration.
   
   I would avoid `--validate=false` here: disabling manifest validation does 
not fix the underlying cluster connection.
   
   We have also prepared an [SSO configuration 
guide](https://github.com/miki3421/openserverless-site/blob/docs-sso-configuration/content/en/docs/installation/configure/sso/_index.md),
 currently proposed for the documentation website in [PR 
#96](https://github.com/apache/openserverless-site/pull/96).
   
   Please share the check results and how your cluster was installed, redacting 
any sensitive details. There is no need to post your full kubeconfig, tokens, 
certificates, or client secret.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to