Open kahirokunn opened 4 months ago
This issue is currently awaiting triage.
If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
User Story
As a developer, I would like to install multiple infrastructures using Helm charts for better management and deployment consistency across GCP and AWS.
Detailed Description
I would like to request the feature to support installing multiple infrastructures (e.g., GCP and AWS) using Helm charts. This could be implemented either by enhancing a single Helm chart to handle multiple providers or by providing separate Helm charts for each provider. Additionally, a comprehensive tutorial on how to configure and deploy these Helm charts for multi-cloud environments would be highly beneficial. This tutorial should cover the necessary steps, configurations, and best practices for managing infrastructure components across GCP and AWS.
Anything else you would like to add:
This feature and accompanying tutorial would greatly benefit users who manage multi-cloud environments, ensuring a unified and streamlined process for infrastructure deployment. It would also reduce the complexity of maintaining separate Helm charts for each provider, providing clear guidance on how to achieve this setup.
/kind feature