-
Notifications
You must be signed in to change notification settings - Fork 825
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
Comments
@ameukam: The label(s) In response to this:
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. |
cc @jeefy |
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]>
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]>
Ref: kubernetes#5127 Add a Route53 public zone used by kops tests. Signed-off-by: Arnaud Meukam <[email protected]>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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]>
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]>
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]>
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]>
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]>
Related to: - kubernetes#5127 Add an EKS cluster that will be used as build cluster for kOps Signed-off-by: Arnaud Meukam <[email protected]>
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]>
/milestone v1.31 |
Ref: - kubernetes/kops#16637 - kubernetes/k8s.io#5127 Ensure E2E and network plugins presubmits runs on community-owned infrastructure. Signed-off-by: Arnaud Meukam <[email protected]>
Ref: - kubernetes/k8s.io#5127 - kubernetes/kops#16637 Update the todo list after: - kubernetes#32922
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@ameukam with all Kops jobs migrated to the new prow clusters, can we close this out or is there additional work to be done? |
@rifelpet migrate the prowjobs was needed to unblock the migration of the prow control plane. Third phase is about:
|
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. |
/milestone v1.32 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
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:
k8s-infra-prow-build-trusted
k8s-infra-prow-build
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
The text was updated successfully, but these errors were encountered: