Repository navigation
feat: add configurable pod scheduling to DevWorkspaceOperatorConfig #1723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tolusha
wants to merge
6
commits into
main
Choose a base branch
from
feat/configurable-pod-scheduling
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+5,701
−76
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: devfile/devworkspace-operator
Length of output: 15144
🏁 Script executed:
Repository: devfile/devworkspace-operator
Length of output: 45683
🏁 Script executed:
Repository: devfile/devworkspace-operator
Length of output: 40414
🏁 Script executed:
Repository: devfile/devworkspace-operator
Length of output: 41727
🏁 Script executed:
Repository: devfile/devworkspace-operator
Length of output: 10528
Do not use workspace-resolved
AuthSecretfor backup jobs.A workspace owner with the standard namespace
editrole can create aDevWorkspaceOperatorConfigin the workspace namespace and setcontroller.devfile.io/devworkspace-configto it. The backup path then accepts itsBackupCronJob.Registry.AuthSecret, reads that-named Secret from the operator namespace, and copies it into the workspace namespace.Use the global configuration for registry-secret selection while retaining the workspace-resolved configuration for other backup settings.
Suggested fix
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we source the operator-namespace authSecret from
GetGlobalConfig()in this shared helper? If I’m reading the flow correctly, namespace editors can create a DWOC that names an operator-namespace Secret, which then gets copied into their namespace. Restore appears to allow this already, and this PR extends it to periodic backups.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 8232
@rohanKanojiaYes.HandleRegistryAuthSecretis the better place to enforce this boundary. My caller-only suggestion would protect backups but leave restore exposed.The helper currently uses the caller’s
AuthSecretto select a Secret from the operator namespace. Both backup and restore pass workspace-resolved configuration.Keep the workspace-namespace Secret lookup first. If that Secret is absent, select the operator-namespace Secret only from
GetGlobalConfig():Use this instead of the current
authSecretNameassignment. If the globalAuthSecretis empty, continue without authentication. Do not fall back to the workspace-resolvedAuthSecret.Retain the workspace-resolved configuration for scheduling and other backup settings. This limits the change to the cross-namespace Secret selection.
Regression coverage should check that:
The finding remains open until the shared-helper change is verified.
You are interacting with an AI system.