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

Sample GcpNfsVolume in docs does not work #358

Closed
tmilos77 opened this issue Jul 19, 2024 · 1 comment · Fixed by #367
Closed

Sample GcpNfsVolume in docs does not work #358

tmilos77 opened this issue Jul 19, 2024 · 1 comment · Fixed by #367
Assignees
Labels
area/documentation Issues or PRs related to documentation kind/bug Categorizes issue or PR as related to a bug.

Comments

@tmilos77
Copy link
Contributor

Description

The sample yaml snippet for GcpNfsVolume from the docs https://kyma-project.io/#/cloud-manager/user/resources/04-30-10-gcp-nfs-volume

apiVersion: cloud-resources.kyma-project.io/v1beta1
kind: GcpNfsVolume
metadata:
  name: my-vol
spec:
  capacityGb: 1024
  location: us-west1

does not work and ends up with the Error condition: googleapi: Error 400: us-west1 is not a valid location for instance creation, it should be a valid GCP zone., badRequest

Expected result

Expected docs samples to work

Actual result

Docs sample does not work

Steps to reproduce

In dev b7695d7 GCP apply

apiVersion: cloud-resources.kyma-project.io/v1beta1
kind: GcpNfsVolume
metadata:
  name: my-vol
spec:
  capacityGb: 1024
  location: us-west1

Troubleshooting

@tmilos77 tmilos77 added kind/bug Categorizes issue or PR as related to a bug. area/documentation Issues or PRs related to documentation labels Jul 19, 2024
@abalaie
Copy link
Contributor

abalaie commented Jul 21, 2024

Tested the sample from the PR dev b7695d7 and it worked.

@abalaie abalaie self-assigned this Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants