Match current KEP template

Author: enj

keps/sig-auth/3331-structured-config-for-oidc-authentication/README.md

@@ -936,6 +936,20 @@ This through this both in small and large cases, again with respect to the
 
 TBA.
 
+###### Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)?
+
+<!--
+Focus not just on happy cases, but primarily on more pathological cases
+(e.g. probes taking a minute instead of milliseconds, failed pods consuming resources, etc.).
+If any of the resources can be exhausted, how this is mitigated with the existing limits
+(e.g. pods per node) or new limits added by this KEP?
+
+Are there any tests that were run/should be run to understand performance characteristics better
+and validate the declared limits?
+-->
+
+TBA.
+
 ### Troubleshooting
 
 ###### How does this feature react if the API server and/or etcd is unavailable?