-
Notifications
You must be signed in to change notification settings - Fork 163
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
Bug 1729242: OCP 4 AWS privilege escalation vulnerability by running pods on masters #524
Closed
ravisantoshgudimetla
wants to merge
1
commit into
openshift:master
from
ravisantoshgudimetla:defaultNodeSelector
Closed
Changes from all commits
Commits
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 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
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
@@ -1,6 +1,7 @@ | ||||
package scheduler | ||||
|
||||
import ( | ||||
configv1 "github.com/openshift/api/config/v1" | ||||
"github.com/openshift/cluster-kube-apiserver-operator/pkg/operator/configobservation" | ||||
"github.com/openshift/library-go/pkg/operator/configobserver" | ||||
"github.com/openshift/library-go/pkg/operator/events" | ||||
|
@@ -10,6 +11,8 @@ import ( | |||
"k8s.io/klog" | ||||
) | ||||
|
||||
const workerNodeSelector = "node-role.kubernetes.io/worker=\"\"" | ||||
|
||||
// ObserveDefaultNodeSelector reads the defaultNodeSelector from the scheduler configuration instance cluster | ||||
func ObserveDefaultNodeSelector(genericListers configobserver.Listers, recorder events.Recorder, existingConfig map[string]interface{}) (map[string]interface{}, []error) { | ||||
listers := genericListers.(configobservation.Listers) | ||||
|
@@ -36,7 +39,12 @@ func ObserveDefaultNodeSelector(genericListers configobserver.Listers, recorder | |||
if err != nil { | ||||
return prevObservedConfig, errs | ||||
} | ||||
|
||||
if schedulerConfig.Spec == (configv1.SchedulerSpec{}) { | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I prefer the defaulting pattern used in: cluster-kube-apiserver-operator/pkg/operator/configobservation/auth/auth_metadata.go Line 52 in 3568cbf
|
||||
if err := unstructured.SetNestedField(observedConfig, workerNodeSelector, defaultNodeSelectorPath...); err != nil { | ||||
errs = append(errs, err) | ||||
} | ||||
klog.V(4).Infof("Found an empty scheduler spec, so setting the defaultNodeSelector to worker nodes") | ||||
} | ||||
defaultNodeSelector := schedulerConfig.Spec.DefaultNodeSelector | ||||
if len(defaultNodeSelector) > 0 { | ||||
if err := unstructured.SetNestedField(observedConfig, defaultNodeSelector, defaultNodeSelectorPath...); err != nil { | ||||
|
This file contains 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
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.
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.
This is not guaranteed to exist in all clusters.
Node roles are not an api and no business logic should based on node roles.
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.
IIUC, there are 2 ways to distinguish master nodes from worker nodes:
So, are you suggesting, we cannot rely on role label which the
defaultNodeSelector
is based on? IIRC, we used to have something liketype=Compute
as defaultNodeSelector in 3.11.This is not to say that we cannot have a validation against pods have master tolerations
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.
@smarterclayton Can you explain what you mean by "Node roles are not an api and no business logic should based on node roles."? It has been common practice with OpenShift in the field to add role labels to nodes and separate workload based on these labels by using node selectors and the
openshift.io/node-selector
annotation. This has been a very effective design pattern, what is inappropriate about this? Should we encourage use of a different label?