-
-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect with Oracle Cloud OCI #3573
Comments
if you need certain permissions to access your cluster then Telepresence also needs to see those permissions. So, for example, if you happen to connect Telepresence without the credentials needed to access the cluster this error can happen. So there might be a permissions issue with Oracle Cloud. But first could you try telepresence quit -s, and then try connecting again? If its an order of operations thing that would resolve it, so it'd be good to rule that out. |
@cindymullins-dw I just tried to run As you see in the kubeconfig file part in my issue, the access to the cluster is managed by the Can I try anything else to help debugging this issue? |
So, I may have find a way to make it work. On another computer, I didn't want to install the OCI CLI so I changed the users:
- name: user-[REDACTED]
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
command: podman
args:
- run
- --rm
- --tty
- --volume
- /home/my-user/.oci:/oracle/.oci:U
- ghcr.io/oracle/oci-cli:latest
- ce
- cluster
- generate-token
- --cluster-id
- [REDACTED]
- --region
- [REDACTED]
env: [] And I don't have ay error when using This is a nice workaround but I don't understand why it does not work correctly when using the OCI CLI directly. |
Thanks very much, @sambonbonne for sharing that workaround. I'll mark this as a feature request in relation to the Oracle Cloud OCI since I don't see a mention (overt support) of it in our docs. |
One thing that comes to mind is that you're using |
@sambonbonne Did you try with a full path to the |
Closing this, because no more info was provided. |
Describe the bug
I started a Kubernetes cluster on Oracle Cloud (OKE service) and installed the Telepresence traffic manager through the Helm chart with ArgoCD without any custom values in the
telepresence
namespace.To use
kubectl
with OKE clusters, I have to use the oci cli, configure it in~/.oci/
and i have the following user in the kubeconfig file:When using
kubetl get nodes
to try the connection, it works perfectly.When manully using the
oci ce cluster generate-token …
command, I see the response from Oracle Cloud with a generated token.But when running
telepresence connect --manager-namespace telepresence
, it seems theoci
command fails.Here are the "direct" logs from the command:
I ran
telepresence gather-logs
but it gives me an empty ZIP file because no logs are produced in~/.cache/telepresence/logs/
.To Reproduce
Steps to reproduce the behavior:
kubectl
to ensure it workstelepresence connect
Expected behavior
Telepresence creates the daemon and I can launch intercepts.
Current behavior
Telepresence fails to run.
Versions
$ telepresence version OSS Client : v2.18.0 OSS Root Daemon: v2.17.0 OSS User Daemon: v2.18.0 Traffic Manager: not connected
OCI CLI: 3.39.0
OS: Arch Linux
I am not using any VPN.
The text was updated successfully, but these errors were encountered: