Render a Page About Each KEP by bupd · Pull Request #618 · kubernetes/contributor-site

bupd · 2026-01-03T12:53:03Z

Summary

Closes #611

This PR adds individual pages for each KEP (Kubernetes Enhancement Proposal) that has progressed beyond the provisional stage. Pages are dynamically generated at build time using Hugo content adapters.

Changes

Add Hugo content adapter to generate KEP pages from existing keps.json data
Add layout templates for individual KEP pages (layouts/keps/)
Update KEP table shortcode to link titles to internal pages
Add stage badge styles (alpha/beta/stable/deprecated)

KEP Page Contents

Each generated page displays:

Title and stage badge
Status
Links to enhancement issue and KEP documentation
Owning SIG with link to community repo
Participating SIGs (if any)
Milestones (alpha/beta/stable versions)
Feature gates with components
Authors, approvers, and reviewers
Timeline (created/last updated dates)
Related KEPs

Implementation Notes

Only KEPs beyond provisional stage are rendered (543 pages)
Provisional KEPs still link to GitHub
Manual markdown overrides supported by creating content/en/resources/keps/{kepNumber}.md
Uses Hugo content adapter for low-overhead maintenance

Signed-off-by: bupd <bupdprasanth@gmail.com>

k8s-ci-robot · 2026-01-03T12:53:10Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bupd
Once this PR has been reviewed and has the lgtm label, please assign natalisucks 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:

OWNERS

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

TineoC · 2026-01-03T14:14:00Z

Hey @bupd, thanks for starting to work on this. When I was checking your preview, I instinctively clicked the KEP Number instead of the KEP Title. Maybe we should consider the best solution for the links in the table as well.

TineoC · 2026-01-03T14:16:13Z

If all the details are covered in the new sub-page, maybe considering adding information that's not hyperlinked (such as the k8s release related to that KEP, for example).

bupd · 2026-01-03T14:17:44Z

If all the details are covered in the new sub-page, maybe considering adding information that's not hyperlinked (such as the k8s release related to that KEP, for example).

Where I can find that info if it's already there somewhere we can do so.

bupd · 2026-01-03T14:18:34Z

Hey @bupd, thanks for starting to work on this. When I was checking your preview, I instinctively clicked the KEP Number instead of the KEP Title. Maybe we should consider the best solution for the links in the table as well.

Also I didn't change the table much just updated the title to lead to the sub page other things remain as before.

Thanks 👍

TineoC · 2026-01-03T14:24:48Z

I need to think about this more. I'll bring it up at the next meeting. There are no blockers on your side; I would appreciate it if you could also add the link to the subpage by clicking the KEP #.

Signed-off-by: bupd <bupdprasanth@gmail.com>

TineoC

<ul class="list-unstyled">
  {{ range $stage, $milestone := $data.milestone }}
    {{ if $milestone }}
    {{- $version := strings.TrimPrefix "v" $milestone -}}
    <li>
      {{ $stage }}:
      <a href="https://github.com/kubernetes/sig-release/tree/master/releases/release-{{ $version }}" class="kep-milestone" target="_blank" rel="noopener noreferrer">
        {{ $milestone }}
      </a>
    </li>
    {{ end }}
  {{ end }}
</ul>

TineoC · 2026-01-03T20:24:46Z

If all the details are covered in the new sub-page, maybe considering adding information that's not hyperlinked (such as the k8s release related to that KEP, for example).

Where I can find that info if it's already there somewhere we can do so.

This could link the kep with the k8s release. Do you think https://github.com/kubernetes/sig-release/tree/master/releases/release-X.Y.Z is a good link to use?

<ul class="list-unstyled">
  {{ range $stage, $milestone := $data.milestone }}
    {{ if $milestone }}
    {{- $version := strings.TrimPrefix "v" $milestone -}}
    <li>
      {{ $stage }}:
      <a href="https://github.com/kubernetes/sig-release/tree/master/releases/release-{{ $version }}" class="kep-milestone" target="_blank" rel="noopener noreferrer">
        {{ $milestone }}
      </a>
    </li>
    {{ end }}
  {{ end }}
</ul>

lmktfy · 2026-01-18T09:29:14Z

I agree with #618 (comment)

Let's try to merge something that adds value without the complexity of making it perfect.

lmktfy · 2026-01-18T09:30:59Z

/kind feature
/retitle Render a Page About Each KEP

lmktfy

/lgtm

How would you like to proceed @bupd? I think we can merge this as-is; if you'd like to polish it more, there are suggestions.

I suggest you only pick the ones that you think will really help.

lmktfy · 2026-01-19T19:33:59Z

layouts/keps/single.html

+  {{/* Stage badge */}}
+  {{ with .Params.stage }}
+  <div class="kep-stage-badge kep-stage-{{ . }}">
+    <span class="badge">{{ . | upper }}</span>
+  </div>
+  {{ end }}


Nice approach.

lmktfy · 2026-01-19T19:34:35Z

layouts/keps/single.html

+    <h2>Links</h2>
+    <ul>
+      <li>
+        <a href="https://features.k8s.io/{{ .Params.kepNumber }}" target="_blank" rel="noopener">


(nit)

Suggested change

<a href="https://features.k8s.io/{{ .Params.kepNumber }}" target="_blank" rel="noopener">

<a href="https://kep.k8s.io/{{ .Params.kepNumber }}" target="_blank" rel="noopener">

lmktfy · 2026-01-19T19:35:33Z

layouts/keps/single.html

+  <div class="kep-sigs mt-4">
+    <h2>SIGs</h2>
+    <p>
+      <strong>Owning SIG:</strong>


Suggested change

<strong>Owning SIG:</strong>

<p class="kep-sigs-owner">Owning SIG:</p>

(and then add an associated stylesheet entry)

lmktfy · 2026-01-19T19:38:46Z

layouts/keps/single.html

+  {{ end }}
+
+  {{/* Feature gates */}}
+  {{ with .Params.featureGates }}


We can maybe one day link to https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#NameGoesHere (or whatever)

Also the Kubernetes website people can - if asked - set up short URLs if we want, eg https://features.k8s.io/gates/NameGoesHere that redirects to https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#NameGoesHere

lmktfy · 2026-01-19T19:39:39Z

layouts/keps/single.html

+  <div class="kep-feature-gates mt-4">
+    <h2>Feature Gates</h2>
+    <table class="table table-sm">
+      <thead>


Extra credit: add a <caption>.

lmktfy · 2026-01-19T19:39:59Z

layouts/keps/single.html

+    {{ with .Params.approvers }}
+    <p>
+      <strong>Approvers:</strong>
+      {{ range $i, $approver := . }}
+        {{- if $i }}, {{ end -}}
+        <a href="https://github.com/{{ trim $approver "@" }}">{{ $approver }}</a>
+      {{ end }}
+    </p>
+    {{ end }}


nit: list these after reviewers

lmktfy · 2026-01-19T19:40:34Z

layouts/keps/single.html

+    <ul>
+      {{ range . }}
+      <li>
+        <a href="https://github.com/kubernetes/enhancements/tree/master{{ . }}">{{ . }}</a>


Maybe we could link to the generated page for the related KEP?

lmktfy · 2026-01-19T19:42:20Z

layouts/keps/single.html

+      {{ range $i, $sig := . }}
+        {{- if $i }}, {{ end -}}
+        <a href="https://github.com/kubernetes/community/tree/master/{{ $sig }}">
+          {{ strings.TrimPrefix "sig-" $sig | humanize | title }}


(nit)

Suggested change

{{ strings.TrimPrefix "sig-" $sig | humanize | title }}

SIG {{ strings.TrimPrefix "sig-" $sig | humanize | title }}

lmktfy · 2026-01-19T19:44:27Z

layouts/keps/single.html

+        {{ with .alpha }}<tr><td>Alpha</td><td>{{ . }}</td></tr>{{ end }}
+        {{ with .beta }}<tr><td>Beta</td><td>{{ . }}</td></tr>{{ end }}
+        {{ with .stable }}<tr><td>Stable</td><td>{{ . }}</td></tr>{{ end }}
+        {{ with .deprecated }}<tr><td>Deprecated</td><td>{{ . }}</td></tr>{{ end }}


Ideally we use special marking to show that future milestones are anticipated, rather than commitments.

lmktfy · 2026-01-19T19:46:25Z

layouts/keps/single.html

+  {{/* Feature gates */}}
+  {{ with .Params.featureGates }}
+  <div class="kep-feature-gates mt-4">
+    <h2>Feature Gates</h2>


(nit)

Suggested change

<h2>Feature Gates</h2>

<h2>Feature Gates</h2>

<p>This enhancement was designed with opt-in or opt-out at the feature level;

there are <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/">feature gates</a> associated with it.</p>

dipesh-rawat · 2026-01-25T12:56:10Z

layouts/keps/single.html

+
+  {{/* External links section */}}
+  <div class="kep-links mt-4">
+    <h2>Links</h2>


Could we consider making these headings linkable by adding anchor links to them?

dipesh-rawat · 2026-01-25T13:03:44Z

layouts/keps/single.html

+  {{ with .Params.seeAlso }}
+  <div class="kep-see-also mt-4">
+    <h2>Related KEPs</h2>
+    <ul>
+      {{ range . }}
+      <li>
+        <a href="https://github.com/kubernetes/enhancements/tree/master{{ . }}">{{ . }}</a>
+      </li>
+      {{ end }}


This block generation logic may need a small tweak, because not all links in the KEP JSON seeAlso attribute point to the k/enhancements repo. Some refer to external sites or other repositories, and the current logic always renders them to the k/enhancements path, which results in 404 links. I have included a few examples below (Refer the Related KEPs section)

https://deploy-preview-618--kubernetes-contributor.netlify.app/resources/keps/1281/

https://deploy-preview-618--kubernetes-contributor.netlify.app/resources/keps/1965/

https://deploy-preview-618--kubernetes-contributor.netlify.app/resources/keps/2332/

https://deploy-preview-618--kubernetes-contributor.netlify.app/resources/keps/1152/

Mmm, yes, let's avoid making an assumption about what this field is set to.

bupd · 2026-01-26T11:04:06Z

Thanks for the review @lmktfy , @dipesh-rawat , @TineoC - will ping you again once i made the requested changes,

Thanks

k8s-ci-robot · 2026-02-07T06:30:56Z

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.

bupd added 3 commits January 3, 2026 18:18

feat(keps): add layout templates for individual KEP pages

a0a1eba

Signed-off-by: bupd <bupdprasanth@gmail.com>

feat(keps): add content adapter to generate KEP pages

3927b48

Signed-off-by: bupd <bupdprasanth@gmail.com>

feat(keps): update shortcode to link to internal KEP pages

99e8246

Signed-off-by: bupd <bupdprasanth@gmail.com>

k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 3, 2026

k8s-ci-robot requested review from mrbobbytables and reylejano January 3, 2026 12:53

k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 3, 2026

feat(keps): update index page type and add KEP styles

6865886

Signed-off-by: bupd <bupdprasanth@gmail.com>

bupd force-pushed the kep-pages branch from a6e4dd6 to 6865886 Compare January 3, 2026 16:43

TineoC reviewed Jan 3, 2026

View reviewed changes

k8s-ci-robot changed the title ~~Feat: Render a Page About Each KEP~~ Render a Page About Each KEP Jan 18, 2026

k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 18, 2026

lmktfy reviewed Jan 19, 2026

View reviewed changes

k8s-ci-robot assigned lmktfy Jan 19, 2026

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 19, 2026

dipesh-rawat reviewed Jan 25, 2026

View reviewed changes

k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 7, 2026

	<a href="https://features.k8s.io/{{ .Params.kepNumber }}" target="_blank" rel="noopener">
	<a href="https://kep.k8s.io/{{ .Params.kepNumber }}" target="_blank" rel="noopener">

	<strong>Owning SIG:</strong>
	<p class="kep-sigs-owner">Owning SIG:</p>

	{{ strings.TrimPrefix "sig-" $sig \| humanize \| title }}
	SIG {{ strings.TrimPrefix "sig-" $sig \| humanize \| title }}

Conversation

bupd commented Jan 3, 2026

Summary

Changes

KEP Page Contents

Implementation Notes

Uh oh!

k8s-ci-robot commented Jan 3, 2026

Uh oh!

TineoC commented Jan 3, 2026

Uh oh!

TineoC commented Jan 3, 2026

Uh oh!

bupd commented Jan 3, 2026

Uh oh!

bupd commented Jan 3, 2026

Uh oh!

TineoC commented Jan 3, 2026

Uh oh!

TineoC left a comment

Choose a reason for hiding this comment

Uh oh!

TineoC commented Jan 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lmktfy commented Jan 18, 2026

Uh oh!

lmktfy commented Jan 18, 2026

Uh oh!

lmktfy left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bupd commented Jan 26, 2026

Uh oh!

k8s-ci-robot commented Feb 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

TineoC commented Jan 3, 2026 •

edited

Loading