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.

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

Extend RuntimeCR to be able to define CIRDs for ingress filtering in Runtime CR #637

Open
2 tasks
tobiscr opened this issue Jan 30, 2025 · 0 comments
Open
2 tasks

Extend RuntimeCR to be able to define CIRDs for ingress filtering in Runtime CR #637

tobiscr opened this issue Jan 30, 2025 · 0 comments
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.

Comments

@tobiscr
Copy link
Contributor

tobiscr commented Jan 30, 2025 •
edited
Loading

Description

Extend the RuntimeCR and add a field / array to define CIRDs. It should consider the option to define filtering rules per worker pool.

  • Align with @kyma-project/gopher how this field will look like and how it can be supported on BTP UI side.
  • Extend the RuntimeCR model to support a new field for specifying ingress filtering rules.

Reasons

Support Ingress filtering in Kyma.

Attachments
@tobiscr tobiscr added area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature. labels Jan 30, 2025
@tobiscr tobiscr changed the title Extend RuntimeCR to be able to define CIRDr which have to be blocked by Gardener's runtime CR Extend RuntimeCR to be able to define CIRDs for ingress filtering in Runtime CR Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/control-plane Related to all activities around Kyma Control Plane kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tobiscr