Skip to content
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

feat(core)!: Introduce two new CRDs and update existing ones #35

Merged
merged 4 commits into from
Jan 15, 2024
Merged

feat(core)!: Introduce two new CRDs and update existing ones #35

merged 4 commits into from
Jan 15, 2024

Conversation

anurag-rajawat
Copy link
Collaborator

@anurag-rajawat anurag-rajawat commented Jan 11, 2024

Description

Fixes #34

Does this PR introduce a breaking change?
Yes.

Checklist

  • PR title follows the <type>: <description> convention
  • I use conventional commits in my commit messages
  • I have updated the documentation accordingly
  • I Keep It Small and Simple: The smaller the PR is, the easier it is to review and have it merged
  • I have performed a self-review of my code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Additional information for reviewer

Hold off on merging this PR for now. The CRDs' status field is still under development and need to be finalized before this PR can be integrated.

Mention if this PR is part of any design or a continuation of previous PRs

Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
@anurag-rajawat anurag-rajawat marked this pull request as draft January 12, 2024 06:19
type NimbusFromSource struct {
Path string `json:"path,omitempty"`
RuleAction string `json:"action"`
Mode string `json:"mode,omitempty"`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add some description for each field

FromSource []SyscallFromSource `json:"fromSource,omitempty"`
}
// Mode defines the enforcement behavior of the intent.
// Defaults to best-effort.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mention "strict" here, and also what it means

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mention "strict" here

We'll be updating our documentation to list all possible field values, so I don't think there's a need to mention strict here.

what it means

Mode defines the enforcement behavior of the intent.

Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
@anurag-rajawat
Copy link
Collaborator Author

ClusterNimbusPolicies are temporarily not supported by the nimbus-kubearmor adapter.

@anurag-rajawat anurag-rajawat marked this pull request as ready for review January 13, 2024 17:39
@anurag-rajawat anurag-rajawat marked this pull request as draft January 13, 2024 17:41
Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
@anurag-rajawat
Copy link
Collaborator Author

ClusterNimbusPolicies are temporarily not supported by the nimbus-kubearmor adapter.

This issue has been fixed.

Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
@anurag-rajawat anurag-rajawat marked this pull request as ready for review January 15, 2024 16:44
@seungsoo-lee seungsoo-lee merged commit 8e1950f into 5GSEC:main Jan 15, 2024
9 checks passed
@anurag-rajawat anurag-rajawat deleted the feat-crds-spec branch January 16, 2024 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cleanup code: Implement new CRD for Intent with ID, params
3 participants