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

Missing step in tutorial #18018

Open
alexsavio opened this issue Jan 22, 2024 · 5 comments
Open

Missing step in tutorial #18018

alexsavio opened this issue Jan 22, 2024 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alexsavio
Copy link

What Happened?

The page here: https://minikube.sigs.k8s.io/docs/tutorials/local_path_provisioner/
It doesn't tell exactly what to do with the yaml file presented.

Attach the log file

--

Operating System

None

Driver

None

@liangyuanpeng
Copy link
Contributor

It doesn't tell exactly what to do with the yaml file presented.

local-path-provisioner is working for it and not minikube if you're talking about the yaml file of PersistentVolumeClaim.

@alexsavio
Copy link
Author

What I mean is that the tutorial says: The following yaml creates PVC and Pod that creates file with content on second node (minikube-m02): but if you follow the tutorial from the beginning, there is no mention about what is this yaml about or what the reader should do with the yaml file to continue the tutorial section.

@T-Lakshmi
Copy link

I think its worth to add a command to create pvc and pod with the give yaml file.
/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 1, 2024
@T-Lakshmi
Copy link

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Feb 1, 2024
@T-Lakshmi
Copy link

Fixes are welcome to improve docs here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants