fix: Prevent permission errors for ignored workload types #996 #1013
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.
Fix permission errors when workload types are ignored
Problem
The original PR #997 attempted to fix issue #996 but only addressed part of the problem. While it prevented reloading of ignored workload types, it didn't prevent the initial listing of those resources, which still caused permission errors.
What was happening:
--ignored-workload-types=jobs,cronjobsand removed RBAC permissions for Jobs/CronJobsFailed to list cronjobs/jobs: cronjobs.batch is forbiddenFault in previous PR:
The original fix only added checks in the
ShouldReloadfunction, but thedoRollingUpgradefunction was still callingrollingUpgradefor Jobs and CronJobs, which internally tries to list these resources regardless of the ignore flags.Solution
Modified
doRollingUpgradefunction ininternal/pkg/handler/upgrade.goto check ignored workload types before attempting to list/process Jobs and CronJobs:Testing
Test Environment:
--ignored-workload-types=jobs,cronjobsTest Results:
Before Fix (upstream image):
After Fix:
Validation:
Impact
Closes #996