Merged
Conversation
4d0f56e to
a2ef786
Compare
a2ef786 to
b605c59
Compare
ignacioboud
reviewed
Nov 20, 2025
ignacioboud
approved these changes
Nov 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Tenemos un scope de Scheduled Task que está definido como un override del base scope "k8s".
Esto implica que los clientes que quieran usar este scope, no podían alterar el comportamiento del Scheduled Task dado que sólo soportamos un nivel de overrides.
Este PR agrega soporte a múltiples levels de overrides, permitiendo hacer cosas como:
El orden de resolución de los overrides es por orden en el que se especifican, el útlimo override es el último que se resuelve (y por ende el de mayor prioridad).
Adicionalmente este PR introduce unos cambios para que la lógica de gestión de Service Accounts funcione para Scheduled Task