-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix psp in config manifests #13327
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
Fix psp in config manifests #13327
Conversation
Codecov ReportBase: 86.50% // Head: 86.50% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #13327 +/- ##
=======================================
Coverage 86.50% 86.50%
=======================================
Files 196 196
Lines 14544 14544
=======================================
Hits 12581 12581
Misses 1664 1664
Partials 299 299 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
@skonto perhaps makes sense (here or different PR) to also use 1.25 w/ the |
|
@matzew yeah we should test eventually on 1.25 on a workflow (added to TODO) but not sure if the project is ready for the migration so I am holding this PR anyway. Out of curiosity will try it here. |
|
/retest |
|
All tests pass will add the 1.25 flow and see if there is any difference. |
26b562c to
e67979d
Compare
|
@psschwei, I am trying 1.25 and we have a dependency that fails, (afaik knative repos are not on v1 could it be the kapp one?): /cc @evankanderson |
|
The update to the latest for metallb also does not work out of the box eg. ingress fails: Also cant use the current on 1.25 due to the psps which are not available. Will revert. Adding 1.25 on github flows needs a separate PR. cc @matzew |
|
I can take a look later tonight; I'm surprised that our other testing passed on those platforms. |
|
@evankanderson any update on this one? :) |
Yeah, I think that's it... I opened carvel-dev/kapp#620 to report it.
I've had issues with that too when trying to set it up locally (haven't had a chance to look into why yet). Did the tests work with the old version? |
No because the old version of metallb defines psps that are removed in 1.25, we need that last version. |
|
@psschwei or @evankanderson gentle ping for a merge. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evankanderson, skonto The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test gateway-api-latest |
* fix sc * revert github flow change
* fix sc * revert github flow change
* Fix psp in config manifests (knative#13327) * fix sc * revert github flow change * remove seccomp profile * fix indentation * fix deployments scs for ci and release
* Fix psp in config manifests (knative#13327) * fix sc * revert github flow change * remove seccomp profile * fix indentation * fix deployments scs for ci and release
* Fix psp in config manifests (knative#13327) * fix sc * revert github flow change * remove seccomp profile * fix indentation * fix deployments scs for ci and release
* Fix psp in config manifests (knative#13327) * fix sc * revert github flow change * remove seccomp profile * fix indentation * fix deployments scs for ci and release
* Fix psp in config manifests (knative#13327) * fix sc * revert github flow change * remove seccomp profile * fix indentation * fix deployments scs for ci and release Co-authored-by: Stavros Kontopoulos <skontopo@redhat.com>
* I believe this [PR](knative/serving#13327) adds it to the controller in the serving repo, but why not do it in the net-contour repo too?
* believe this [PR](knative/serving#13327) adds the seccompProfile part to the third_party resources in serving, but I think we should do it in this repo too
* believe this [PR](knative/serving#13327) adds the seccompProfile part to the third_party resources in serving, but I think we should do it in this repo too
* believe this [PR](knative/serving#13327) adds the seccompProfile part to the third_party resources in serving, but I think we should do it in this repo too
* I believe this [PR](knative/serving#13327) adds it to the controller in the serving repo, but why not do it in the net-contour repo too?
* I believe this [PR](knative/serving#13327) adds it to the controller in the serving repo, but why not do it in the net-contour repo too?
* believe this [PR](knative/serving#13327) adds the seccompProfile part to the third_party resources in serving, but I think we should do it in this repo too Co-authored-by: Clay Kauzlaric <ckauzlaric@vmware.com>
* I believe this [PR](knative/serving#13327) adds it to the controller in the serving repo, but why not do it in the net-contour repo too? Co-authored-by: Clay Kauzlaric <ckauzlaric@vmware.com>
Fixes partially #13308 for podsecuritypolicy (deprecated since 1.21, will be unavailable on 1.25) as we need to support the Pod Security Admission instead which becomes stable in 1.25.
makes all pods not launching. Errors are as follows on the versions tested 1.23+ (events in the corresponding ns):
allwithALLin capabilities section because that is the only acceptable string check here and here.