cluster-api-provider-gcp

cluster-api-provider-gcp copied to clipboard

/kind documentation

Describe the solution you'd like [A clear and concise description of what you want to happen.] Adding a Custom Virtual Network documentation GCP

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.] Refer to https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/docs/book/src/topics/custom-vnet.md for better understanding Also: https://cloud.google.com/vpc/docs/vpc https://cloud.google.com/vpc/docs/using-vpc

/good-first-issue

@sayantani11: This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

/assign

@daemon1024 Updates?

@daemon1024 Any updates? Stuck somewhere?

@sayantani11 Apologies for the delay and missing providing updates here.

So I went through the shared resources and the spec provided here https://github.com/kubernetes-sigs/cluster-api-provider-gcp/blob/main/config/crd/bases/infrastructure.cluster.x-k8s.io_gcpclusters.yaml

I came with a rough configuration...

---

Existing subnet

```yaml
apiVersion: infrastructure.cluster.x-k8s.io/v1Alpha4
kind: GCPCluster
spec:
    network:
        autoCreateSubnetworks: false
        name: my-vpc
        subnets:
            - name: my-subnet
            cidrBlock: 10.0.32.0/20
    project: xyz
    region: us-easta
```

New subnet, provide cidrblock

```yaml
apiVersion: infrastructure.cluster.x-k8s.io/v1Alpha4
kind: GCPCluster
spec:
    network:
        autoCreateSubnetworks: false
        name: my-vpc
        subnets:
            - name: my-subnet
            cidrBlock: 10.0.32.0/20
            region: ? # do we need it when we have region specified in spec?
    project: xyz
    region: us-easta
```

Auto cidr block ranges - https://cloud.google.com/vpc/docs/vpc#ip-ranges

---

But I am not sure how do I test it out! I don't have GCP instance 😓

@daemon1024 You can try creating a gcp account and I guess you get a 250$ credit in the start that you can use or you can try using qwicklabs I believe

@daemon1024 And yes I think we need to specify region in the subnet as well

@daemon1024 or you can try reaching me on slack... I will try testing it... But will need some time with that😅

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

Hey @sayantani11 is this still up for grab, maybe I can give a try

Yes! /assign @AvineshTripathi

/remove-lifecycle stale

@sayantani11 I did go through the resources but being new to kubernetes I need some time and more resource to get a better idea so I was wondering if you can help me with resources with more basics to clear my fundamentals

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

/lifecycle frozen /help

/remove-lifecycle stale

/lifecycle frozen