You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-apps/4017-pod-index-label/README.md
-5Lines changed: 0 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -283,8 +283,6 @@ How will UX be reviewed, and by whom?
283
283
Consider including folks who also work outside the SIG or subproject.
284
284
-->
285
285
286
-
<<[UNRESOLVED how this change will interact with existing workloads]>>
287
-
288
286
One thing that must be considered is how enabling this new feature will interact with existing workloads. There are a couple of options:
289
287
290
288
1. Only inject the label on *newly created pods*, so an existing StatefulSet/Indexed Jobs may include pods with the label and some without it.
@@ -306,9 +304,6 @@ ensure consistency within a single StatefulSet/Indexed Job and therefore a more
306
304
After considering these trade-offs, I propose we move forward with Option 1 for simplicity and to avoid being stuck adding this annotation to
307
305
StatefulSets/Indexed Jobs. In addition, the downside of existing workloads having only a subset of pods with the new label will not cause any serious issues.
0 commit comments