miki3421 commented on issue #271: URL: https://github.com/apache/openserverless/issues/271#issuecomment-6178385345
Thanks @col-panic, this clarifies the problem. Your local `kubectl` has no active context, but the kubeconfig may already have been downloaded by OPS into its own directory rather than `~/.kube/config`. Please run: ```bash ops -info ``` Look for `OPS_TMP`. With the default configuration, check: ```bash ls -l "$HOME/.ops/tmp/kubeconfig" kubectl --kubeconfig="$HOME/.ops/tmp/kubeconfig" config current-context kubectl --kubeconfig="$HOME/.ops/tmp/kubeconfig" cluster-info ``` If `OPS_TMP` shows a different directory, use that path instead. If the file is missing, OPS provides a command to retrieve it from your K3s server: ```bash ops cloud k3s kubeconfig YOUR_SERVER YOUR_SSH_USER ``` Use the same server and SSH user used during installation. This retrieves the configuration; it does not reinstall the cluster. Then repeat the connection check. Once `cluster-info` succeeds, explicitly pass the same kubeconfig when running your original SSO command: ```bash env KUBECONFIG="$HOME/.ops/tmp/kubeconfig" ops config sso keycloak ... ``` Replace `...` with your existing Keycloak options. If the connection check now reports a timeout or certificate error, please share that error with sensitive details redacted. That would identify a separate connectivity or TLS issue. There is no need to share the kubeconfig itself. -- 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]
