Skip to content

feat : Karmor support for non k8s installation #484

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.

Sign up for GitHub

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

Jump to bottom
Open
Aryan-sharma11 opened this issue Jan 30, 2025 · 2 comments · May be fixed by #475
Open

feat : Karmor support for non k8s installation #484

Aryan-sharma11 opened this issue Jan 30, 2025 · 2 comments · May be fixed by #475

Comments

@Aryan-sharma11
Copy link
Member

Karmor client should able to install kubearmor in non kubernetes environment (docker/systemd).

Deliverables:

  1. As a docker container:
    • docker compose should be configurable( visibility, default posture etc) and embedded in cli tool itself. we can make use of golang embed library for this.
    • karmor uninstall should work
  2. As a systemd service
    • Kubearmor tar can be downloaded via github releases or from docker registeries.
    • Kubearmorconfig.yaml should be configurable here too, the config file will also be embedded along with the tool itself.
    • Karmor uninstall should work.
@Aryan-sharma11 Aryan-sharma11 linked a pull request Jan 30, 2025 that will close this issue
Open
@itsCheithanya
Copy link

itsCheithanya commented Jan 31, 2025 •
edited
Loading

  • Kubearmorconfig.yaml should be configurable here too, the config file will also be embedded along with the tool itself.

@Aryan-sharma11 can you elaborate on this?

@Aryan-sharma11
Copy link
Member Author

Aryan-sharma11 commented Feb 13, 2025 •
edited
Loading

  • Kubearmorconfig.yaml should be configurable here too, the config file will also be embedded along with the tool itself.

@Aryan-sharma11 can you elaborate on this?

Sure @itsCheithanya, by configurable I mean that the config values like visibility and maxalertpersec that are passed here should be dynamically handled by karmorcli, to achieve this, either we can generate the yaml files inside karmor tool itself or we can use templates
for ref templates , embed
similarly in case of docker-compose we should dynamically populate these fields

itsCheithanya added a commit to itsCheithanya/kubearmor-client that referenced this issue Mar 9, 2025
@itsCheithanya
Fixes: kubearmor#484 Karmor support for non k8s installation
4b435a2
Aryan-sharma11 pushed a commit to itsCheithanya/kubearmor-client that referenced this issue Apr 10, 2025
@itsCheithanya @Aryan-sharma11
Fixes: kubearmor#484 Karmor support for non k8s installation
5b0ccad
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support karmor install for non-k8s environment itsCheithanya/kubearmor-client
2 participants
@Aryan-sharma11 @itsCheithanya