cluster-api-provider-cloudstack icon indicating copy to clipboard operation
cluster-api-provider-cloudstack copied to clipboard
verified publisher icon kubernetes-sigs

Allow Project-Level Resource Creation

Open rgjrt1 opened this issue 2 years ago • 11 comments

/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

rgjrt1 avatar Feb 15 '23 20:02 rgjrt1

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

k8s-triage-robot avatar May 16 '23 20:05 k8s-triage-robot

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

ozhankaraman avatar Jun 01 '23 10:06 ozhankaraman

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

k8s-triage-robot avatar Jul 01 '23 10:07 k8s-triage-robot

This capability is still needed.

rgjrt1 avatar Jul 26 '23 21:07 rgjrt1

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

rohityadavcloud avatar Sep 20 '23 06:09 rohityadavcloud

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

g-gaston avatar Nov 01 '23 21:11 g-gaston

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

k8s-triage-robot avatar Jan 20 '24 09:01 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

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 avatar Jan 20 '24 09:01 k8s-ci-robot

/reopen

rgjrt1 avatar Jan 20 '24 22:01 rgjrt1

@rgjrt1: Reopened this issue.

In response to this:

/reopen

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 avatar Jan 20 '24 22:01 k8s-ci-robot

/remove-lifecycle rotten

rohityadavcloud avatar Feb 08 '24 12:02 rohityadavcloud

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

k8s-triage-robot avatar May 08 '24 12:05 k8s-triage-robot

/remove-lifecycle stale

vishesh92 avatar May 09 '24 07:05 vishesh92