Hi there @carlosbenicio79,

It is quite possible that your Jenkins service is running as a different user so it does not have access to the Kubernetes config file of your SSH user.

What you could do is add an extra step in your Jenkinsfile to first authenticate with doctl, it would look something like this:

doctl auth init --access-token "your_digitalocean_token"

I would recommend adding your DigitalOcean access token as a Jenkins secret rather than hardcoding it in your Jenkinsfile.

And then add another step to save the Kubernetes config:

doctl kubernetes cluster kubeconfig save use_your_cluster_name

Hope that this helps!
Regards,
Bobby

Hi @bobbyiliev

Thank you for answering me.

I solved it changing the approaching by using kubernetes plugin.

;)