Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AKS Learn feedback: "Statically provision a volume" annotated with pv.kubernetes.io/provisioned-by #123600

Open
mloskot opened this issue Jul 2, 2024 · 2 comments

Comments

@mloskot
Copy link
Contributor

mloskot commented Jul 2, 2024

Type of issue

Other (describe below)

Feedback

In the Statically provision a volume section there is this example, copied below, which displays use of pv.kubernetes.io/provisioned-by annotation:

apiVersion: v1
kind: PersistentVolume
metadata:
  annotations:
    pv.kubernetes.io/provisioned-by: file.csi.azure.com
  name: azurefile
spec:
  ...

while the Kubernetes documentation on Well-Known Labels, Annotations and Taints indicates this annotation should correspond to dynamic provisioning, screenshot with the section pasted below:

image


The lack of explanation on why the example uses the annotation makes the example confusing to reader.

Page URL

https://learn.microsoft.com/en-us/azure/aks/azure-csi-files-storage-provision#statically-provision-a-volume

Content source URL

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/azure-csi-files-storage-provision.md

Author

@tamram

Document Id

b95ca0b2-e809-a149-dec7-a15ac2146ee1


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@mloskot mloskot changed the title AKS Learn feedback: Statically provision a volume annotated with pv.kubernetes.io/provisioned-by AKS Learn feedback: "Statically provision a volume" annotated with pv.kubernetes.io/provisioned-by Jul 2, 2024
@TPavanBalaji
Copy link
Contributor

@mloskot
Thanks for your feedback! We will investigate and update as appropriate.

@SaibabaBalapur-MSFT
Copy link
Contributor

@mloskot
I'm going to assign this to the document author so they can take a look at it accordingly.

@tamram
Please review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants