You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Until recently, CI/CD tools have been using the default secret token to authenticate to OKE for deployment purposes. Now that OKE uses Kubeconfig v2, this approach will not work anymore.
Community Note
Description
Until recently, CI/CD tools have been using the default secret token to authenticate to OKE for deployment purposes. Now that OKE uses Kubeconfig v2, this approach will not work anymore.
Solution: create a service account that CI/CD tools can use to authenticate for deployment purposes.
https://docs.cloud.oracle.com/iaas/Content/ContEng/Tasks/contengaddingserviceaccttoken.htm
References
The text was updated successfully, but these errors were encountered: