Update docs for VPC integration

[vishesh92]

Issue #, if available:

Description of changes:

Testing performed:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vishesh92

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vishesh92]

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

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-cloudstack ready!

Name	Link
🔨 Latest commit	00f1659
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-cloudstack/deploys/681473cf728405000800e9bc
😎 Deploy Preview	https://deploy-preview-434--kubernetes-sigs-cluster-api-cloudstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Copilot]

Pull Request Overview

This PR updates the documentation for VPC integration in CloudStack clusters. It expands the existing network configuration instructions to include details on creating and managing VPC resources, adds CLI examples for listing VPCs, and provides a sample YAML configuration snippet to illustrate the setup.

Comments suppressed due to low confidence (1)

docs/book/src/clustercloudstack/configuration.md:76

• Verify that the jq filter '.vpc[]' correctly matches the output of 'cmk list vpcs'. If the output key is plural or different, update the filter for consistency.

cmk list vpcs listall=true zoneid=<zoneid> | jq '.vpc[] | {name, id}'

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.78%. Comparing base (d597e80) to head (00f1659).
Report is 102 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #434      +/-   ##
==========================================
+ Coverage   25.66%   25.78%   +0.11%     
==========================================
  Files          59       72      +13     
  Lines        5563     6778    +1215     
==========================================
+ Hits         1428     1748     +320     
- Misses       3996     4865     +869     
- Partials      139      165      +26     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[weizhouapache]

lgtm

@kiranchavala
can you please have a look as well

[kiranchavala]

@vishesh92 In the network documentation section

Can we split the documentation for each network type in cloudstack with an example.

https://deploy-preview-434--kubernetes-sigs-cluster-api-cloudstack.netlify.app/clustercloudstack/configuration#network

There are many variables which may cause some confusion.

CLOUDSTACK_NETWORK_NAME
CLOUDSTACK_VPC_NAME
with-existing-vpc-network
with-kube-vip
CLUSTER_ENDPOINT_IP

For example can we say

Currenty, there are 5 types of network in Cloudsack and provide the env value or sample yaml file detail for each network type

1. Isolated network 

CLOUDSTACK_NETWORK_NAME
CLUSTER_ENDPOINT_IP=192.168.1.161
CLUSTER_ENDPOINT_PORT=6443

2. VPC network 

CLOUDSTACK_VPC_NAME
CLOUDSTACK_NETWORK_NAME( tier name) 
clusterctl generate  

-- flavor with-existing-vpc-network


3. Shared network
CLOUDSTACK_NETWORK_NAME

4. Routed Isolated network

CLOUDSTACK_NETWORK_NAME
clusterctl generate  

-- flavor with-existing-vpc-network
--flavor with-kube-vip \

5. Routed VPC network 

CLOUDSTACK_VPC_NAME
CLOUDSTACK_NETWORK_NAME( tier name) 
clusterctl generate  

-- flavor with-existing-vpc-network
--flavor with-kube-vip \

[vishesh92]

@kiranchavala I have updated the docs a little bit. As of now, for using the flavor with-existing-vpc-network requires an extra environment variable for the VPC name. The default & with-kube-vip flavor requires the same environment variables to be defined.