Doc about Persistent disk added

[sayantani11]

What type of PR is this?

What this PR does / why we need it:
This PR adds documentation how persistent disks should be provisioned and attached to VMs in Google Cloud Platform.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

Persistent disk documentation

[k8s-ci-robot]

Hi @sayantani11. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign gab-satchi after the PR has been reviewed.
You can assign the PR to them by writing /assign @gab-satchi in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sayantani11]

#451

[shivanshuraj1333]

Hey, it's a good practice to link the issue using Ref: <issue> in PR description, whenever the PR is subpart of the issue.

[sayantani11]

Hey, it's a good practice to link the issue using Ref: <issue> in PR description, whenever the PR is subpart of the issue.

The issue was actually made after I pushed the changes 😅

[cpanato]

/ok-to-test

[sayantani11]

@cpanato https://cloud.google.com/deployment-manager/docs/step-by-step-guide/create-a-configuration
Tried to follow the configuration as stated here.

[sayantani11]

/kind documentation

[sayantani11]

/retest

[sayantani11]

@cpanato guess this should work

[cpanato]

@cpanato guess this should work

can you run and post the results to we make sure that works?

[sayantani11]

/hold

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale