feat!: remove autoscaling configuration and apply miscellaneous fixes #73
Conversation
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
BetoFandino
approved these changes
Nov 25, 2025
The autoscaling configuration has long been unmaintained and should be instead handled by https://github.com/eduNEXT/tutor-contrib-pod-autoscaling. The variable used to install extra packages in the sandbox virtual environment was not properly configured as a default variable. The apparmor-loader deamon set was not using the same image as the docker deployment, and the generated config-maps where missing appropriate labels.
MoisesGSalas
force-pushed
the
mgs/small-fixes
branch
from
9f66290 to
e625881
Compare
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.
The autoscaling configuration has long been unmaintained and should be instead handled by https://github.com/eduNEXT/tutor-contrib-pod-autoscaling.
The variable used to install extra packages in the sandbox virtual environment was not properly configured as a default variable.
The apparmor-loader deamon set was not using the same image as the docker deployment, and the generated config-maps where missing appropriate labels.