chore: remove the Kubernetes plugin feature gate - #199
Merged
Conversation
The Kubernetes parser and provider plugins are now active for everyone, so the enableK8sPlugins run-parameter gate can go. Removes EnableK8sPlugins and SkipPluginExecution from plugins.Config, the RequiresK8sPlugins marker and gatedPluginNames helper, the project-skip branch in ScanProject, and Scanner.applyFeatureFlags along with both call sites. Nothing else read the run parameters' featureFlags blob, so the field and its GraphQL selection are dropped too.
liamg
approved these changes
Jul 31, 2026
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
2 participants
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 Kubernetes parser and provider plugins are now active for everyone, so the
enableK8sPluginsrun-parameter gate can go.Changes
pkg/plugins/config.go— drop theEnableK8sPluginsfield and theSkipPluginExecutionmethod.ProviderPluginsno longer filters and just returns what the manager loads.pkg/plugins/required.go— drop theRequiresK8sPluginsmarker onrequiredPluginand thegatedPluginNames()helper. The two kubernetes entries stay inrequiredPlugins; they were always downloaded regardless, since the gate only ever affected execution.pkg/scanner/scan.go— drop the branch that returnednil, nilto skip projects handled by a gated parser.ScanProjectno longer has a nil-success path, so the correspondingprojectResult == nilcheck in the caller goes too.internal/scanner/scanner.go— removeScanner.applyFeatureFlagsand both call sites (ListPolicies,Scan).internal/api/dashboard/client.go— with the gate gone nothing readRunParameters.FeatureFlags, so the field and itsfeatureFlagsGraphQL selection are removed.Net: 156 lines deleted, 24 added. No behaviour change for orgs that already had the flag on; orgs that didn't now get Kubernetes scanning.