cluster-api-provider-aws icon indicating copy to clipboard operation
cluster-api-provider-aws copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Ability to add machines to clusters based on a different infra provider

Open andrewrynhard opened this issue 4 years ago • 9 comments
trafficstars

/kind feature

Describe the solution you'd like

As a user I would like to manage AWS instances with cluster-api-provider-aws, but join them to a control plane that is not in AWS. The idea is that I can use Sidero for bare metal, and then burst out to AWS when I need to.

Anything else you would like to add:

I want to create a MachineDeployment using cluster-api-provider-aws , and have them join a non-AWSCluster cluster:

I1022 22:07:53.051213       1 awsmachine_controller.go:164] controller-runtime/manager/controller/awsmachine "msg"="AWSCluster or AWSManagedControlPlane is not ready yet" "cluster"="workspace" "machine"="workspace-workers-aws-75bc69fdcd-pbnj9" "name"="workspace-workers-g8vnb" "namespace"="cluster-workspace" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="AWSMachine"

The cluster is based on Sidero.

Environment:

  • Cluster-api-provider-aws version: 0.7.0
  • Kubernetes version: (use kubectl version): v1.22.2
  • OS (e.g. from /etc/os-release): Talos v0.13.0

andrewrynhard avatar Oct 22 '21 22:10 andrewrynhard

/triage accepted /milestone backlog /priority backlog

richardcase avatar Nov 29 '21 18:11 richardcase

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

k8s-triage-robot avatar Feb 27 '22 19:02 k8s-triage-robot

/remove-lifecycle stale

richardcase avatar Mar 15 '22 15:03 richardcase

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

k8s-triage-robot avatar Jun 13 '22 16:06 k8s-triage-robot

/lifecycle frozen

richardcase avatar Jun 14 '22 06:06 richardcase

/remove-lifecycle frozen

richardcase avatar Jul 12 '22 16:07 richardcase

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

k8s-triage-robot avatar Oct 10 '22 16:10 k8s-triage-robot

/triage accepted /priority important-longterm

richardcase avatar Oct 11 '22 10:10 richardcase

/remove-lifecycle stale

richardcase avatar Oct 11 '22 10:10 richardcase

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

k8s-triage-robot avatar Jan 09 '23 10:01 k8s-triage-robot

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

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

k8s-triage-robot avatar Feb 19 '24 05:02 k8s-triage-robot