Skip to content

Move CAPI forks to rancher org #2264

@salasberryfin

Description

@salasberryfin

Description

The forked CAPI provider repositories are still under the rancher-sandbox organization. They should be moved to rancher.

Affected repositories are:

  • cluster-api
  • cluster-api-provider-aws
  • cluster-api-provider-azure
  • azure-service-operator
  • cluster-api-provider-gcp
  • cluster-api-provider-vsphere
  • cluster-api-operator
  • cluster-api-provider-metal3
  • ip-address-manager

We should send a request to EIO to move this to rancher.

Metadata

Metadata

Assignees

Labels

area/dependencyIssues or PRs related to dependency changesarea/providerskind/cleanupCategorizes issue or PR as related to cleaning up code, process, or technical debt.

Type

No fields configured for Task.

Projects

Status

Blocked

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions