-
Notifications
You must be signed in to change notification settings - Fork 920
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
Modifying apiVersion for daemonset and adding selectors #1005
Conversation
Co-authored-by: Lorenzo Fontana <lo@linux.com> Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com> Signed-off-by: Rushabh Sanghvi <rushabh268@gmail.com>
Co-authored-by: Lorenzo Fontana <lo@linux.com> Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com> Signed-off-by: Rushabh Sanghvi <rushabh268@gmail.com>
Signed-off-by: Rushabh Sanghvi <rushabh268@gmail.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @rushabh268! It looks like this is your first PR to falcosecurity/falco 🎉 |
/assign @mstemm |
Signed-off-by: Rushabh Sanghvi <rushabh268@gmail.com> Signed-off-by: Rushabh Sanghvi <rushabh268@gmail.com>
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.
Hi @rushabh268 - thanks for fixing this! Can you please address my comment and do the same in falco-daemonset-configmap-slim.yaml
and in k8s-without-rbac/falco-service.yaml
?
integrations/k8s-using-daemonset/k8s-with-rbac/falco-daemonset-configmap.yaml
Outdated
Show resolved
Hide resolved
Also @rushabh268 please sign-off your commit. E.g:
or if you want to sign the last commit you did:
|
@fntlnz I have made the suggested changes and also made the necessary changes to integrations/k8s-using-daemonset/falco-event-generator-deployment.yaml. I have also signed off the last commit. |
3e6e22b
to
ae6edd4
Compare
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.
Hey @rushabh268 thanks for doing this!
Any chance you can also do it for falco-daemonset-configmap-slim.yaml and k8s-without-rbac/falco-service.yaml ? :)
…-configmap.yaml Co-Authored-By: Lorenzo Fontana <fontanalorenz@gmail.com>
/check-dco |
Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits. 📝 Please follow instructions in the contributing guide to update your commits with the DCO Full details of the Developer Certificate of Origin can be found at developercertificate.org. The list of commits missing DCO signoff:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/milestone 0.21.0 |
Removing this from the milestone since we have to make a community decision on how to handle those. Same comment as this one #1044 (comment) This kind of thing doesn't really need to cut a release. :) |
@leogr this is the PR I was mentioning to you before, too |
Superseded by #1044 /close |
@leodido: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area integrations
What this PR does / why we need it:
This PR fixes the case where Falco daemonset cannot be deployed in Kubernetes 1.17+ due to incorrect apiVersion and missing selector for pods
Which issue(s) this PR fixes:
#993
Automatically closes linked issue when PR is merged.
Usage:
Fixes #993
.Fixes #993
Special notes for your reviewer:
This should fix the following errors:
Does this PR introduce a user-facing change?: