Unable to authenticate with api

  • Posted on February 15, 2022
  • JacqueGMAsked by JacqueGM

I moved from to and i cannot manage to make ingress work.

The terraform plan keeps failing although I check the troubleshoting guide from specifically at these lines: $ curl --cacert /var/run/secrets/ -H "Authorization: Bearer $(cat /var/run/secrets/" https://kubernetes.default.svc.cluster.local && echo but connection cannot be established still getting a 403

I checked at the configuration of kubectl and it looks that this is still using v1betav1 however this configuration I got kubconfig I got from the cluster… so I dont really get why is not v1 there…

any hint will be highly appreaciated

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
August 7, 2022

Hi there,

Is it possible for you to share the complete YAML file? It is possible that only changing the version might not work out of the box without some changes.

For example, here are some of the notable changes:

  • spec.backend is renamed to spec.defaultBackend
  • The backend serviceName field is renamed to
  • Numeric backend servicePort fields are renamed to service.port.number
  • String backend servicePort fields are renamed to
  • pathType is now required for each specified path. Options are Prefix, Exact, and ImplementationSpecific. To match the undefined v1beta1 behavior, use ImplementationSpecific.



Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up