@oondemand/oon-core-back 0.7.21 → 0.7.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/src/delivery/runtime.js +7 -1
package/package.json
CHANGED
package/src/delivery/runtime.js
CHANGED
|
@@ -209,10 +209,16 @@ spec:
|
|
|
209
209
|
spec:
|
|
210
210
|
serviceAccountName: oon-runtime
|
|
211
211
|
terminationGracePeriodSeconds: ${TERMINATION_GRACE_SECONDS}
|
|
212
|
+
# DoNotSchedule: com ScheduleAnyway as 2 réplicas de Apps globais ficaram
|
|
213
|
+
# no mesmo nó. Com maxSkew 1 o pod extra do rolling update ainda cabe e,
|
|
214
|
+
# com um único nó, o desvio é zero e nada fica pendente.
|
|
212
215
|
topologySpreadConstraints:
|
|
213
216
|
- maxSkew: 1
|
|
214
217
|
topologyKey: kubernetes.io/hostname
|
|
215
|
-
whenUnsatisfiable:
|
|
218
|
+
whenUnsatisfiable: DoNotSchedule
|
|
219
|
+
# Só os pods da mesma revisão: sem isso, ao fim do rolling update os
|
|
220
|
+
# pods novos podem ficar todos no mesmo nó.
|
|
221
|
+
matchLabelKeys: [pod-template-hash]
|
|
216
222
|
labelSelector:
|
|
217
223
|
matchLabels: { app.kubernetes.io/name: ${context.appCode} }
|
|
218
224
|
imagePullSecrets: [{ name: ${infra.REGISTRY_PULL_SECRET_NAME || "ghcr-oon"} }]
|