Commit 0bf7a6b
ciliumendpoint-gc: skip ciliumendpoints which are too new
I have see real production occurrences when a ciliumendpoint was just
created, but then immediately deleted by cilium operator. The timing is
a strong indicator that we have hit this [known flaw][1] where it is
possible to delete a ciliumendpoint because the operator haven't
received the pod notification. To reduce the chance of this happenning
further, I propose that we wait for at least one interval before
starting to delete a just-created ciliumendpoint.
[1]: https://github.com/cilium/cilium/blob/2e216d1d735073932074497e1687c73bc2f56d1f/operator/endpointgc/gc.go#L134-L137
Signed-off-by: Haibing Zhou <zhouhaibing089@gmail.com>1 parent 0b60dac commit 0bf7a6b
2 files changed
Lines changed: 16 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
156 | 156 | | |
157 | 157 | | |
158 | 158 | | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
159 | 169 | | |
160 | 170 | | |
161 | 171 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
61 | | - | |
| 61 | + | |
62 | 62 | | |
63 | 63 | | |
64 | 64 | | |
| |||
134 | 134 | | |
135 | 135 | | |
136 | 136 | | |
137 | | - | |
| 137 | + | |
138 | 138 | | |
139 | 139 | | |
140 | 140 | | |
| |||
170 | 170 | | |
171 | 171 | | |
172 | 172 | | |
| 173 | + | |
| 174 | + | |
| 175 | + | |
| 176 | + | |
173 | 177 | | |
174 | 178 | | |
175 | 179 | | |
| |||
0 commit comments