Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS: migrate kOps away from CNCF account #5127

Open
ameukam opened this issue Apr 13, 2023 · 15 comments
Open

AWS: migrate kOps away from CNCF account #5127

ameukam opened this issue Apr 13, 2023 · 15 comments
Assignees
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Milestone

Comments

@ameukam
Copy link
Member

ameukam commented Apr 13, 2023

All kOps e2e tests currently run under the CNCF management account.

There should be migrated to the AWS Kubernetes organization or any community infrastructure.

Phase 1: Periodics jobs
We should start with the periodics and migrate them on those build clusters:

  • e2e-kops-do-* : k8s-infra-prow-build-trusted
  • e2e-kops-gce-*: k8s-infra-prow-build
  • e2e-kops-aws-*: k8s-infra-kops-prow-build

It's not trivial to identify how a job belongs to a specific build cluster so they will be multiple tentatives

Phase 2: Presubmits & Postsubmits
Once we have confidence that the periodics can run on the community infrastructure we can follow up with presubmits and postsubmits.

/assign @ameukam @justinsb
/area aws
/area infra/aws
/priority important-soon
/milestone v1.28

@ameukam ameukam added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Apr 13, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone Apr 13, 2023
@k8s-ci-robot k8s-ci-robot added the area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure label Apr 13, 2023
@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 13, 2023
@k8s-ci-robot
Copy link
Contributor

@ameukam: The label(s) area/aws cannot be applied, because the repository doesn't have them.

In response to this:

All kOps e2e tests currently run under the CNCF management account.

There should be migrated to the AWS Kubernetes organization.

/assign @ameukam @justinsb
/area aws
/area infra/aws
/priority important-soon
/milestone v1.28

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.

@ameukam
Copy link
Member Author

ameukam commented Apr 13, 2023

cc @jeefy

ameukam added a commit to ameukam/k8s.io that referenced this issue Apr 14, 2023
Ref: kubernetes#5127

- `kops-infra-ci` will be used to run e2e tests until we switch to
  boskos
- `kops-infra-services` will be used to provision services needed to run
  kops e2e tests like Route53 or S3.

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Apr 14, 2023
Ref: kubernetes#5127

- `kops-infra-ci` will be used to run e2e tests until we switch to
  boskos
- `kops-infra-services` will be used to provision services needed to run
  kops e2e tests like Route53 or S3.

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Apr 19, 2023
Ref: kubernetes#5127

Add a Route53 public zone used by kops tests.

Signed-off-by: Arnaud Meukam <[email protected]>
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 12, 2023
@ameukam
Copy link
Member Author

ameukam commented Jul 12, 2023

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 12, 2023
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Setup the terraform config needed to build the kOps CI infrastructure in
the community infrastructure

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Setup the terraform config needed to build the kOps CI infrastructure in
the community infrastructure

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Add a VPC IPAM pool used to manage the IP addresses used by the VPC

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Create a VPC that will be used to create the EKS cluster for kOps CI.
The CIDR 10.128.0.0/16 is used and splitted different the different azs
of us-east-2 region.

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Create a VPC that will be used to create the EKS cluster for kOps CI.
The CIDR 10.128.0.0/16 is used and splitted different the different azs
of us-east-2 region.

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/k8s.io that referenced this issue Aug 8, 2023
Related to:
  - kubernetes#5127

Add an EKS cluster that will be used as build cluster for kOps

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/test-infra that referenced this issue Mar 8, 2024
ameukam added a commit to ameukam/test-infra that referenced this issue Mar 11, 2024
Related to:
  - kubernetes/k8s.io#5127

Migrate presubmits to k8s-infra with exclusion of those testing kops
upgrades.

Signed-off-by: Arnaud Meukam <[email protected]>
ameukam added a commit to ameukam/test-infra that referenced this issue Mar 12, 2024
Related to:
  - kubernetes/k8s.io#5127

Migrate presubmits to k8s-infra with exclusion of those testing kops
upgrades.

Signed-off-by: Arnaud Meukam <[email protected]>
@ameukam
Copy link
Member Author

ameukam commented Apr 18, 2024

/milestone v1.31

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2024
@ameukam
Copy link
Member Author

ameukam commented Jul 17, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 17, 2024
@rifelpet
Copy link
Member

@ameukam with all Kops jobs migrated to the new prow clusters, can we close this out or is there additional work to be done?

@ameukam
Copy link
Member Author

ameukam commented Jul 23, 2024

@rifelpet migrate the prowjobs was needed to unblock the migration of the prow control plane. Third phase is about:

  • migrate away from s3://k8s-kops-prow
  • rotate or drop the usage of the AWS static credentials for the E2E tests

@BenTheElder
Copy link
Member

rotate or drop the usage of the AWS static credentials for the E2E tests

is that directly related to moving to the kubernetes specific accounts?

@ameukam
Copy link
Member Author

ameukam commented Jul 23, 2024

rotate or drop the usage of the AWS static credentials for the E2E tests

is that directly related to moving to the kubernetes specific accounts?

if you mean the AWS specific accounts, yes. we need to migrate to only one k8s-owned AWS account (kops-infra-ci). Currently we use the CNCF account.

@ameukam
Copy link
Member Author

ameukam commented Aug 21, 2024

/milestone v1.32

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.31, v1.32 Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Status: 🏗 In progress
Development

No branches or pull requests

6 participants