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
How could Official Azure Provider help solve your problem?
We can have a separate managed resource that's implemented in Go and continuously refreshes the token in its connection secret, similar to ClusterAuth in AWS EKS.
The text was updated successfully, but these errors were encountered:
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!
What problem are you facing?
In AKS, clusters are accessed through kubelogin with short-lived tokens similar to how EKS clusters have short-lived tokens. See more details here https://azure.github.io/kubelogin/cli/get-token.html and here crossplane-contrib/provider-kubernetes#105
How could Official Azure Provider help solve your problem?
We can have a separate managed resource that's implemented in Go and continuously refreshes the token in its connection secret, similar to
ClusterAuth
in AWS EKS.The text was updated successfully, but these errors were encountered: