-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Adding preset to use Azure resources, moving 2022 master job to azure #32998
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -230,18 +230,17 @@ periodics: | |
testgrid-dashboards: sig-windows-master-release, sig-windows-signal | ||
testgrid-tab-name: capz-windows-containerd-master-serial-slow-hpa | ||
- name: ci-kubernetes-e2e-capz-master-windows-2022 | ||
cluster: k8s-infra-prow-build | ||
interval: 3h | ||
decorate: true | ||
decoration_config: | ||
timeout: 4h | ||
labels: | ||
preset-dind-enabled: "true" | ||
preset-kind-volume-mounts: "true" | ||
preset-azure-cred-wi: "true" | ||
preset-azure-anonymous-pull: "true" # Sets REGISTRY which is needed when building CCM/CNM images | ||
preset-azure-community: "true" | ||
preset-capz-windows-common: "true" | ||
preset-capz-containerd-1-7-latest: "true" | ||
preset-windows-private-registry-cred: "true" | ||
preset-capz-windows-2022: "true" | ||
extra_refs: | ||
- org: kubernetes-sigs | ||
|
@@ -259,7 +258,6 @@ periodics: | |
path_alias: sigs.k8s.io/cloud-provider-azure | ||
workdir: false | ||
spec: | ||
serviceAccountName: prowjob-default-sa | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What was the reasoning behind dropping this? We dont need this anymore? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I understood we only needed this to "simulate" the community infra service account config, and once we migrated this is the configuration we will expect by default. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Its not needed in the community cluster, the default service account will work |
||
containers: | ||
- image: gcr.io/k8s-staging-test-infra/kubekins-e2e:v20240705-131cd74733-master | ||
command: | ||
|
@@ -273,6 +271,9 @@ periodics: | |
requests: | ||
cpu: 2 | ||
memory: "9Gi" | ||
limits: | ||
cpu: 2 | ||
memory: "9Gi" | ||
annotations: | ||
testgrid-alert-email: kubernetes-provider-azure@googlegroups.com, sig-windows-leads@kubernetes.io | ||
testgrid-dashboards: sig-windows-master-release | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a note this will break the test
Kubernetes e2e suite.[It] [sig-node] Container Runtime blackbox test when running a container with a new image should be able to pull from private registry with secret [NodeConformance]
we are tracking fixing this in kubernetes-sigs/windows-testing#446