Skip to content

Conversation

@medyagh
Copy link
Member

@medyagh medyagh commented Jan 9, 2026

This PR could be reviewed after this #36183

with all yaml files linted with the new Linter. I made two PRs for easier review

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/config Issues or PRs related to code in /config area/conformance Issues or PRs related to kubernetes conformance tests area/jobs area/kro Issues or PRs related to KRO area/provider/aws Issues or PRs related to aws provider area/provider/azure Issues or PRs related to azure provider area/provider/gcp Issues or PRs related to gcp provider area/provider/openstack Issues or PRs related to openstack provider area/provider/vmware Issues or PRs related to vmware provider area/prow/bump Updates to the k8s prow cluster area/release-eng Issues or PRs related to the Release Engineering subproject sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/etcd Categorizes an issue or PR as relevant to SIG Etcd. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. sig/network Categorizes an issue or PR as relevant to SIG Network. labels Jan 9, 2026
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jan 13, 2026
@alvaroaleman alvaroaleman removed their request for review January 13, 2026 03:24
…mt, updating dependencies and build scripts.
…, env:) to be indented 2 spaces relative to their parent key. The original template sometimes had them at the same level or aligned incorrectly. We shifted them to match the standard.

- Removing "Invisible" Newlines: Loop and Option tags in Jinja (like {% if %}) leave behind blank lines by default. We changed them to {%- if -%} (adding hyphens) to tell Jinja: "Execute this logic, but strip the whitespace around it." This stopped valid code from being pushed apart by random blank lines.

- Stripping the End: We added {%- endfilter -%} at the very end. This removes all trailing newlines from the template output itself, giving the Python script full control over how jobs are separated.
…red, we ensure that:

There is exactly one newline between jobs (separating them cleanly).
There is exactly one newline at the end of the file (making it a valid text file).
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 13, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: medyagh
Once this PR has been reviewed and has the lgtm label, please assign dims for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 13, 2026
@k8s-ci-robot
Copy link
Contributor

@medyagh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-test-infra-gubernator dff9e8a link true /test pull-test-infra-gubernator
pull-test-infra-prow-checkconfig dff9e8a link true /test pull-test-infra-prow-checkconfig
pull-test-infra-verify-lint b72f839 link true /test pull-test-infra-verify-lint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 13, 2026
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

Details

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.

@SergeyKanzhelev SergeyKanzhelev moved this from Triage to Archive-it in SIG Node CI/Test Board Jan 14, 2026
@lauralorenz
Copy link

This PR doesn't touch anything related to sig multicluster, and the k/k Makefile and hack scripts also doesn't affect any sig multicluster projects because they are all out of tree.

/remove-label sig-multicluster

@k8s-ci-robot
Copy link
Contributor

@lauralorenz: The label(s) /remove-label sig-multicluster cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

This PR doesn't touch anything related to sig multicluster, and the k/k Makefile and hack scripts also doesn't affect any sig multicluster projects because they are all out of tree.

/remove-label sig-multicluster

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.

@lauralorenz
Copy link

/remove-sig multicluster

@k8s-ci-robot k8s-ci-robot removed the sig/multicluster Categorizes an issue or PR as relevant to SIG Multicluster. label Jan 21, 2026
@BenTheElder
Copy link
Member

This PR doesn't touch anything related to sig multicluster, and the k/k Makefile and hack scripts also doesn't affect any sig multicluster projects because they are all out of tree.

It must be touching a directory with OWNERS configured to label sig-multi-cluster, if SIG multi-cluster doesn't own anything here, please send a PR to remove this configuration.

The OWNERS-based label application is evaluated on every push, because the set of files can change on every push.

I think in this case, the issue is a previous iteration had applied auto-formatting to all yaml config files, which would've touched e.g. this folder:


Sorry, we still need additional reviews on this one, cc @pohly for dra.jinja

generate-jobs.py LGTM, and I think conceptual +1 overall from myself, @aojea @upodroid

posting to #sig-testing

@upodroid
Copy link
Member

+1 from me

{%- if run_if_changed and presubmit %}
run_if_changed: {{run_if_changed}}
{%- endif -%}
{%- set indent_width = 4 if not ci else 2 -%}
Copy link
Contributor

Choose a reason for hiding this comment

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

That indention is different between periodics and presubmits is annoying also when copy-and-pasting between them manually, but that ship has sailed a long time ago...

Thanks for coming up with a solution.

run_if_changed: {{run_if_changed}}
{%- endif -%}
{%- set indent_width = 4 if not ci else 2 -%}
{%- filter indent(width=indent_width, first=True) -%}
Copy link
Contributor

Choose a reason for hiding this comment

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

Is the removal of the empty line before each job intentional because yamlfmt complains?

I find the YAML a bit easier to read when different jobs are separated a bit more. If we can have the empty line, then let's keep it. With this patch there is one more empty line after the header, but that is okay and perhaps even better because of consistency:

diff --git a/config/jobs/kubernetes/sig-node/dra.jinja b/config/jobs/kubernetes/sig-node/dra.jinja
index ca7244aa98..13aa089add 100644
--- a/config/jobs/kubernetes/sig-node/dra.jinja
+++ b/config/jobs/kubernetes/sig-node/dra.jinja
@@ -7,7 +7,7 @@ presubmits:
   kubernetes/kubernetes:
 {%- endif %}
 {%- endif %}
-{% if not ci %}
+{%- if not ci %}
 {%- set testgrid_dashboards = testgrid_dashboards + ", sig-node-presubmits" %}
 {%- endif -%}
 {%- if "crio" in job_name %}
@@ -22,8 +22,9 @@ presubmits:
 {%- set testgrid_dashboards = testgrid_dashboards + ", sig-release-master-informing" %}
 {%- set testgrid_alert_email = testgrid_alert_email + ", release-team@kubernetes.io" %}
 {%- endif -%}
-{%- set indent_width = 4 if not ci else 2 -%}
-{%- filter indent(width=indent_width, first=True) -%}
+{%- set indent_width = 2 if ci else 4 -%}
+{% filter indent(width=indent_width, first=True) %}
+
 - name: {{job_name}}
   cluster: {{cluster}}
   {%- if ci %}
diff --git a/hack/generate-jobs.py b/hack/generate-jobs.py
index 2e7ee98847..55d4767290 100755
--- a/hack/generate-jobs.py
+++ b/hack/generate-jobs.py
@@ -99,7 +99,6 @@ def generate_one(path: pathlib.Path, verify: bool) -> typing.List[str]:
                         )
                     )
                     header = ""
-                tmp.write("\n")
             out = template_path.parent / f"{template_path.stem}-{name}.yaml"
             if not os.path.exists(out):
                 if verify:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects area/config Issues or PRs related to code in /config area/conformance Issues or PRs related to kubernetes conformance tests area/jobs area/kro Issues or PRs related to KRO area/provider/aws Issues or PRs related to aws provider area/provider/azure Issues or PRs related to azure provider area/provider/gcp Issues or PRs related to gcp provider area/provider/openstack Issues or PRs related to openstack provider area/provider/vmware Issues or PRs related to vmware provider area/prow/bump Updates to the k8s prow cluster area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/etcd Categorizes an issue or PR as relevant to SIG Etcd. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/security Categorizes an issue or PR as relevant to SIG Security. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/windows Categorizes an issue or PR as relevant to SIG Windows. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. wg/device-management Categorizes an issue or PR as relevant to WG Device Management.

Projects

Archived in project
Status: Needs Triage
Status: Archive-it
Status: No status

Development

Successfully merging this pull request may close these issues.

7 participants