-
Notifications
You must be signed in to change notification settings - Fork 426
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
Fixes for running on k8s 1.23 and restricted PodSecurityAdmission level #1477
Conversation
This commit updates our plumbing dependency to pull in tektoncd/plumbing#1251 which updates the GKE image to cos_containerd. The older cos image is no longer supported as of GKE v1.23. Part of tektoncd#1475 Signed-off-by: Dibyo Mukherjee <[email protected]>
Running into PSP issues:
|
This commit drops the Triggers PodSecurityPolicy since its deprecated and is going to be removed in Kubernetes 1.25 in favor of PodSecurityAdmission. In addition, it adds the `securityContext` required for the "restricted" PodSecurityAdmission levels. These changes are necessary for Triggers to work with Pipelines v0.41 and higher because tektoncd/pipeline#5652 started enforcing the restricted pod security level for all pods in the `tekton-pipelines` namespace (which includes the triggers controller, webhook, and core interceptor deployments). Fixes tektoncd#1447 and required for tektoncd#1475 Signed-off-by: Dibyo Mukherjee <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: savitaashture The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
🎉
/lgtm
@dibyom I apologize if this is the wrong place to provide feedback on this ticket, but I'm still getting this error on k8s v1.24, pipelines v0.42 and triggers v0.22 (I can confirm that
|
@seunggs are you running an eventlistener in the tekton-pipelines namespace? |
@dibyom Yes, |
ok - a quick workaround will be to run your EL in a different namespace till we add a fix |
@dibyom thanks - I've just changed the tekton-pipelines namespace setting: |
thanks for the prompt replies @dibyom, my temp solution is to set
|
Changes
There are two commits which are both required for Triggers to work with Pipelines v0.41 which requires Kubernetes 1.23.
This commit updates our plumbing dependency to pull in tektoncd/plumbing#1251 which updates the GKE image to cos_containerd. The older cos image is no longer supported as of GKE v1.23.
Part of #1475
This commit drops the Triggers PodSecurityPolicy since its deprecated and is
going to be removed in Kubernetes 1.25 in favor of PodSecurityAdmission.
In addition, it adds the
securityContext
required for the "restricted"PodSecurityAdmission levels. These changes are necessary for Triggers to work
with Pipelines v0.41 and higher because tektoncd/pipeline#5652 started
enforcing the restricted pod security level for all pods in the
tekton-pipelines
namespace (which includes the triggers controller, webhook,and core interceptor deployments).
Fixes #1447 and required for #1475
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes