-
Janet Kuo authored
1. Create controllerrevisions (history) and label pods with template hash for both RollingUpdate and OnDelete update strategy 2. Clean up old, non-live history based on revisionHistoryLimit 3. Remove duplicate controllerrevisions (the ones with the same template) and relabel their pods 4. Update RBAC to allow DaemonSet controller to manage controllerrevisions 5. In DaemonSet controller unit tests, create new pods with hash labels
d02f40a5
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| chaosclient | ||
| clientset_generated | ||
| conditions | ||
| informers/informers_generated | ||
| leaderelection | ||
| listers | ||
| metrics | ||
| retry | ||
| testdata | ||
| tests | ||
| unversioned | ||
| OWNERS |