-
Notifications
You must be signed in to change notification settings - Fork 354
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
Rancher Plugin Integration #992
Comments
This is nice! Imo, it would be ok to club "General" and "Policy Details" together. Process, File, Network will have relevant options. Is there a config change if a new attribute has to be added or do we have to change the code? |
That said I can prolly split it into General and Rules.
It's a code change for now, I will try to figure out how it could be just a config change later. |
Hello @nyrahul and @daemon1024, I'm interested in working on this issue under LFX Spring Mentorship! |
Ref #1591 |
What's the status of this issue? Is it resolved, or are there pending tasks? |
Hey @daemon1024 I'm interested in this issue. Since it is under gsoc 2024, I would love to work on with KubeArmor Rancher Plugin. |
hi @daemon1024 @PrimalPimmy @DelusionalOptimist @kranurag7 I have done the setup of Rancher over my Azure AKS cluster, I have installed some tools using Helm: I have also done the installation of KubeArmor on same cluster, I can see my KubeArmor resources deployed on my cluster using Rancher. I do had a prior working experience with Rancher, as I worked with SUSE under Google Summer of Code 2024. But, I want to know more about Plugin integration. Do we need to install Kubearmor as a Rancher extension. Here, this doc explains about Rancher extension: https://ranchermanager.docs.rancher.com/integrations-in-rancher/rancher-extensions Do we need the same for KubeArmor ? |
@daemon1024 i am also interested in this issue for GSoC 2024. |
An extension for Rancher Manager (^v2.7.0) which allows you to interact with KubeArmor.
Initial Scope
Future Items
Notes :
still in RC yet to be stableReleased Now 🚀 )The text was updated successfully, but these errors were encountered: