-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Set secure-pod-defaults to "enabled" by default #14029
Comments
/unassign @pradnyavmw |
/assign @kauana |
Pairing with @kauana - we've discovered a few things First the migrator job is doing extra patches when it shouldn't need to filed an issue here- knative/pkg#2845 Oddly the empty patch is failing because we're hitting this validation - where the old and new spec are the same (unsure why) and the updater annotation is changing - which our webhook checks reject Even if we relaxed this requirement we observed the empty patch+defaulting triggers the creation of new a revision. It might make sense that this secure defaulting is only done during creation instead of update. Finally, a more generic observation around this entire feature is that when we enable it our own hello world image doesn't work. This also applies to any image that runs as root. Hence enabling this by default will probably break ALOT of users especially for demos etc. Curious what others think? |
Thank you so much Kauana and Dave.
I think first of all we should start with adopting non-root for any images in our docs including hello world. |
I agree
I agree - that gathering data is probably the right thing to do. |
Sounds good. Can I create an issue to make all serving code samples run as non-root? |
Yup sounds good |
cc @evankanderson for input Curious if you have thoughts about the tension here where if we enable this by default it will break a lot of existing deployments and require folks to rewrite their images (if that's even possible for some). |
I wanted to enable this at some point; if you explicitly request the insecure values, they are still allowed. It's just that the defaults will point towards secure values if not set. This will break people who are depending on the insecure values but haven't explicitly specified them. The trade-off is that people who are using the insecure values by accident will move to more secure settings. This mostly helps with defense-in-depth if the application is insecure, so it also isn't a critical defense. |
The non-root part is probably the most disruptive; I'd be okay putting that behind a second flag to roll out the |
Created issue to make knative sample images run as non-root: #14566 |
Following up on Evan's feedback - we can make
|
In what area(s)?
/area API
Describe the feature
As per configmap comment:
serving/config/core/configmaps/features.yaml
Lines 46 to 48 in c91f8c4
It says "probably Knative 1.10" but it is still disabled by default.
I opened this for tracking issue.
/cc @evankanderson
The text was updated successfully, but these errors were encountered: