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
As per the documentation, this data source should give list of secrets associated with the service account, but it is still looking for default secrets not the custom ones because of the kubernetes 1.24 version change.
# data source to get SA accountdata"kubernetes_service_account""customer_namespace_sa" {
metadata {
name="deployment"namespace=var.namespace_name
}
}
output"sa_secret_name" {
value=data.kubernetes_service_account.customer_namespace_sa.secret.0.name
}
Error: Failed to discover the default service account token: Unable to find any service accounts tokens which could have been the default one
│
│ with module.helm_sco_onboard.data.kubernetes_service_account.customer_namespace_sa,
│ on namespace/main.tf line 81, in data "kubernetes_service_account" "customer_namespace_sa":
│ 81: data "kubernetes_service_account" "customer_namespace_sa" {
│
The text was updated successfully, but these errors were encountered:
Please update the issue description and provide all information that is requested by the template. In addition to that, please share the following commands output of the service account you are working with:
Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!
As per the documentation, this data source should give list of secrets associated with the service account, but it is still looking for default secrets not the custom ones because of the kubernetes 1.24 version change.
The text was updated successfully, but these errors were encountered: