Skip to content

AWS: migrate main repos - #6008

Merged
istio-testing merged 16 commits into
istio:masterfrom
Stevenjin8:aws/migrate-main-repos
Sep 2, 2026
Merged

istio-testing merged 16 commits into
istio:masterfrom
Stevenjin8:aws/migrate-main-repos

Conversation

@Stevenjin8

@Stevenjin8 Stevenjin8 commented Aug 18, 2026 •

Copy link
Copy Markdown
Contributor
  • Move tools, istio, release-builder to aws (only master and release-1.31)
  • update repository mappings to point to ghcr.io/istio-testing
  • private jobs still need some work. I would like to merge this as-is and immediately follow up fixing the private jobs. Release branches older than 1.31 should not be affected
  • update our signing key to use an aws one.

Since this is a big change, I'm going to wait for this pr to be approved, apply the changes, fix the things i inevitably miss, and once everything seems good, will request another review and merge.

@Stevenjin8
Stevenjin8 requested a review from a team as a code owner August 18, 2026 14:46
@Stevenjin8 Stevenjin8 added the do-not-merge/hold Block automatic merging of a PR. label Aug 18, 2026
@istio-testing istio-testing added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 18, 2026
@Stevenjin8
Stevenjin8 force-pushed the aws/migrate-main-repos branch from 70cb668 to db31209 Compare August 18, 2026 14:57
@Stevenjin8

Copy link
Copy Markdown
Contributor Author

cc @keithmattix I'm shooting to get an approval by friday morning

@istio-testing istio-testing added the needs-rebase Indicates a PR needs to be rebased before being merged label Aug 19, 2026
@Stevenjin8
Stevenjin8 force-pushed the aws/migrate-main-repos branch from 317b1d6 to 85b0e6b Compare August 20, 2026 14:11
@istio-testing istio-testing added needs-rebase Indicates a PR needs to be rebased before being merged and removed needs-rebase Indicates a PR needs to be rebased before being merged labels Aug 20, 2026
@Stevenjin8
Stevenjin8 force-pushed the aws/migrate-main-repos branch from 85b0e6b to 5c363bc Compare September 1, 2026 16:30
@istio-testing istio-testing removed the needs-rebase Indicates a PR needs to be rebased before being merged label Sep 1, 2026
Comment thread prow/aws/config.yaml
- istio/common-files
- istio/community
- istio/enhancements
- istio/istio

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move do not merge protections to aws

Comment thread prow/aws/config.yaml
- istio/common-files
- istio/community
- istio/enhancements
- istio/istio

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have auto merge come from aws

Comment thread prow/gcp/config.yaml
- istio/client-go
- istio/common-files
- istio/enhancements
- istio/istio

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should not have removed this, gcp still need to watch this, other than the aws/explicitly excluded branches

Comment thread infra/aws/istio/eks.tf
Comment on lines +55 to +70
max_size = 60
desired_size = 1
block_device_mappings = {
root = {
device_name = "/dev/xvda"
ebs = merge(local.gp3_root_volume, { volume_size = 256 })
}
}
labels = { testing = "test-pool" }
}
test2 = {
ami_type = "AL2023_x86_64_STANDARD"
instance_types = ["m7a.4xlarge", "m6a.4xlarge", "m7i.4xlarge", "m6i.4xlarge"]
capacity_type = "SPOT"
min_size = 1
max_size = 30

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I requested an increase in our ON_DEMAND capacity. But we're going to have to do with spot instances for now.

Comment thread infra/aws/istio/iam.tf
}
"prowjob-build-tools" = {
read = ["github_istio-testing_pusher"]
read = ["github_istio-testing_pusher", "testing_ghcr_istio"]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to push to ghcr.io/istio/

Comment on lines -16 to +17
testing = "gcr.io/istio-testing"
prerelease-testing = "gcr.io/istio-prerelease-testing"
testing = "ghcr.io/istio/testing"
prerelease-testing = "ghcr.io/istio/prerelease-testing"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have yet to apply this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the change in format? Do I need to private/delete the ones with the other format?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not a change in format. We're going from gcr-> ghcr

@Stevenjin8 Stevenjin8 removed the do-not-merge/hold Block automatic merging of a PR. label Sep 2, 2026
@istio-testing
istio-testing merged commit 83e04a5 into istio:master Sep 2, 2026
6 checks passed
@istio-testing

Copy link
Copy Markdown
Collaborator

@Stevenjin8: Updated the config configmap in namespace default at cluster default using the following files:

  • key config.yaml using file prow/gcp/config.yaml
Details

In response to this:

  • Move tools, istio, release-builder to aws (only master and release-1.31)
  • update repository mappings to point to ghcr.io/istio-testing
  • private jobs still need some work. I would like to merge this as-is and immediately follow up fixing the private jobs. Release branches older than 1.31 should not be affected
  • update our signing key to use an aws one.

Since this is a big change, I'm going to wait for this pr to be approved, apply the changes, fix the things i inevitably miss, and once everything seems good, will request another review and merge.

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-sigs/prow repository.

@istio-testing

Copy link
Copy Markdown
Collaborator

@Stevenjin8: Updated the following 2 configmaps:

  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file prow/aws/config.yaml
  • job-config configmap in namespace default at cluster default using the following files:
    • key istio-private.istio.master.gen.yaml using file ``
    • key istio-private.istio.master.gen.yaml using file prow/aws/cluster/jobs/istio-private/istio/istio-private.istio.master.gen.yaml
    • key istio-private.istio.release-1.31.gen.yaml using file ``
    • key istio-private.istio.release-1.31.gen.yaml using file prow/aws/cluster/jobs/istio-private/istio/istio-private.istio.release-1.31.gen.yaml
    • key istio-private.release-builder.master.gen.yaml using file ``
    • key istio-private.release-builder.master.gen.yaml using file prow/aws/cluster/jobs/istio-private/release-builder/istio-private.release-builder.master.gen.yaml
    • key istio-private.release-builder.release-1.31.gen.yaml using file ``
    • key istio-private.release-builder.release-1.31.gen.yaml using file prow/aws/cluster/jobs/istio-private/release-builder/istio-private.release-builder.release-1.31.gen.yaml
    • key istio.istio.master.gen.yaml using file ``
    • key istio.istio.master.gen.yaml using file prow/aws/cluster/jobs/istio/istio/istio.istio.master.gen.yaml
    • key istio.istio.release-1.31.gen.yaml using file ``
    • key istio.istio.release-1.31.gen.yaml using file prow/aws/cluster/jobs/istio/istio/istio.istio.release-1.31.gen.yaml
    • key istio.istioexperimental.gen.yaml using file ``
    • key istio.istioexperimental.gen.yaml using file prow/aws/cluster/jobs/istio/istio/istio.istioexperimental.gen.yaml
    • key istio.release-builder.master.gen.yaml using file ``
    • key istio.release-builder.master.gen.yaml using file prow/aws/cluster/jobs/istio/release-builder/istio.release-builder.master.gen.yaml
    • key istio.release-builder.release-1.31.gen.yaml using file ``
    • key istio.release-builder.release-1.31.gen.yaml using file prow/aws/cluster/jobs/istio/release-builder/istio.release-builder.release-1.31.gen.yaml
    • key istio.tools.master.gen.yaml using file ``
    • key istio.tools.master.gen.yaml using file prow/aws/cluster/jobs/istio/tools/istio.tools.master.gen.yaml
    • key istio.tools.release-1.31.gen.yaml using file ``
    • key istio.tools.release-1.31.gen.yaml using file prow/aws/cluster/jobs/istio/tools/istio.tools.release-1.31.gen.yaml
Details

In response to this:

  • Move tools, istio, release-builder to aws (only master and release-1.31)
  • update repository mappings to point to ghcr.io/istio-testing
  • private jobs still need some work. I would like to merge this as-is and immediately follow up fixing the private jobs. Release branches older than 1.31 should not be affected
  • update our signing key to use an aws one.

Since this is a big change, I'm going to wait for this pr to be approved, apply the changes, fix the things i inevitably miss, and once everything seems good, will request another review and merge.

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-sigs/prow repository.

dgn added a commit to dgn/istio-test-infra that referenced this pull request Sep 4, 2026
Chart and image both push to ghcr.io/istio/testing/ztunnel:<tag>,
so whichever runs last wins the tag. Point Helm chart publishing at
a /charts subpath instead. Seems to have been a typo in
istio#6008.
istio-testing pushed a commit that referenced this pull request Sep 4, 2026
Chart and image both push to ghcr.io/istio/testing/ztunnel:<tag>,
so whichever runs last wins the tag. Point Helm chart publishing at
a /charts subpath instead. Seems to have been a typo in
#6008.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants