Allow Project-Level Resource Creation

[rgjrt1]

/kind feature

Describe the solution you'd like
Currently, the CAPI provider creates cluster resources at the account level but has no provision to create them within the context of a Project. In theory, one may be able to specify the project's account id, but these accounts are hidden via the listProject API (hardcoded in Cloudstack) so the CAPI provider fails to find the account. This effectively makes it impossible to utilize the CAPI provider in Cloudstack deployments that utilize Projects for multi-team "tenant" access.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-provider-cloudstack version: v0.4.8
• Kubernetes version: (use kubectl version): v1.26.1
• OS (e.g. from /etc/os-release): Rocky Linux 9.1

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ozhankaraman]

Hi, do we have any plan to support this on upcoming release?

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[rgjrt1]

This capability is still needed.

[rohityadavcloud]

Thanks @rgjrt1 @ozhankaraman we'll review if that's an easy fix, otherwise move this to v0.5.0 milestone.

[g-gaston]

Moving to v0.5.0 since this is a new feature and we are only prioritizing vital bugfixes for v0.4.9

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned