Fix prr's comment

Author: HirazawaUi

keps/prod-readiness/sig-node/3721.yaml

@@ -1,3 +1,3 @@
 kep-number: 3721
 alpha:
-  approver: "@jpbetz"
+  approver: "@soltysh"

keps/sig-node/3721-support-for-env-files/README.md

@@ -446,10 +446,11 @@ with this new fields:
 
 ###### Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?
 
-Automated tests will cover the scenarios with and without the changes proposed
-on this KEP. As defined under [Version Skew Strategy](#version-skew-strategy),
+We will manually attempt an upgrade-downgrade test with the following scenario.
+
+As defined under [Version Skew Strategy](#version-skew-strategy),
 we are assuming the cluster may have kubelets with older versions (without
-this KEP' changes), therefore this will be covered of following new tests:
+this KEP' changes):
 
 1. When the kubelet is upgraded, the env files will be instantiated in the
    container. On downgrade, the env files will be ignored but the pod will still
@@ -483,15 +484,17 @@ CONFIG_VAR=HELLO
 
 ###### What are the reasonable SLOs (Service Level Objectives) for the enhancement?
 
-N/A
+SLI: Startup latency of schedulable stateful pods, excluding time to pull images, run init containers, provision volumes (in delayed binding mode) and unmount/detach volumes (from previous pod if needed), measured from pod creation timestamp to when all its containers are reported as started and observed via watch, measured as 99th percentile over last 5 minutes.
+
+SLO: In default Kubernetes installation, 99th percentile per cluster-day1 <= X where X depends on storage provider
 
 ###### What are the SLIs (Service Level Indicators) an operator can use to determine the health of the service?
 
-N/A
+We can determine whether the service is healthy by checking if the started_containers_errors_total and started_pods_errors_total metrics are abnormally increasing.
 
 ###### Are there any missing metrics that would be useful to have to improve observability of this feature?
 
-N/A
+No
 
 ### Dependencies
 
@@ -515,7 +518,7 @@ No
 
 ###### Will enabling / using this feature result in increasing size or count of the existing API objects?
 
-No
+We have added the `fileKeyRef` data structure to `podSpec`, which will undoubtedly increase the size of the Pod API. The increase in size depends on the number of environment variables defined by the user, making it impossible to estimate the exact number of bytes added. However, this should not have a significant impact on the API. For many users, it merely involves migrating environment variables previously defined in `ConfigMap/Secret` to this new structure.
 
 ###### Will enabling / using this feature result in increasing time taken by any operations covered by existing SLIs/SLOs?
 
@@ -527,7 +530,7 @@ No
 
 ###### Can enabling / using this feature result in resource exhaustion of some node resources (PIDs, sockets, inodes, etc.)?
 
-No
+Environment variables are not typically associated with PIDs, sockets, or inodes. However, non-standard usage patterns may introduce risks. For example: if expanded variables are used to launch numerous network services or open excessive file descriptors (e.g., environment variables defining large numbers of port numbers), this could indirectly lead to socket exhaustion.
 
 ### Troubleshooting
 

keps/sig-node/3721-support-for-env-files/kep.yaml

@@ -37,8 +37,9 @@ feature-gates:
     components:
       - kube-apiserver
       - kubelet
-disable-supported: false
+disable-supported: true
 
 # The following PRR answers are required at beta release
 metrics:
-  - N/A
+  - started_containers_errors_total
+  - started_pods_errors_total