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
Resource kubernetes_persistent_volume should expose secret_namespace argument for azure_file volume type, consistently with k8s api
Empirically, this feature become almost necessary with AKS/K8S version 1.19. When spec.azureFile.secretNamespace is not specified, with version 1.18 pods would lookup for azure file secret in their own namespace, with version 1.19 they look that up in the default namespace.
Potential Terraform Configuration
resource"kubernetes_persistent_volume""data" {
metadata {
name="my-data-pv"
}
spec {
capacity={
storage ="100Gi"
}
access_modes=["ReadWriteMany"]
storage_class_name="azurefile"persistent_volume_source {
azure_file {
secret_namespace="my-namespace"# Here is the argument yet to be supported in TF providersecret_name="bla"share_name="blabla"read_only="false"
}
}
mount_options=[
...
]
}
}
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
I also need this because we've upgraded our AKS to 1.19 and the persistent volume stopped working. As a workaround we've moved our secret to the default namespace but we'd like to have this done properly by setting the secret_namespace.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Apr 29, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Resource
kubernetes_persistent_volume
should exposesecret_namespace
argument forazure_file
volume type, consistently with k8s apiEmpirically, this feature become almost necessary with AKS/K8S version 1.19. When spec.azureFile.secretNamespace is not specified, with version 1.18 pods would lookup for azure file secret in their own namespace, with version 1.19 they look that up in the default namespace.
Potential Terraform Configuration
Community Note
The text was updated successfully, but these errors were encountered: