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

Inspect API support for top-level targetRef sectionName #12361

Open
lobkovilya opened this issue Dec 23, 2024 · 0 comments · May be fixed by #12644
Open

Inspect API support for top-level targetRef sectionName #12361

lobkovilya opened this issue Dec 23, 2024 · 0 comments · May be fixed by #12644
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Milestone
2.10.x

Comments

@lobkovilya
Copy link
Contributor

lobkovilya commented Dec 23, 2024 •
edited
Loading

Description

With the new design it'll be possible select a single inbound port for configuration. Once #12375 is implemented we should be able to update the Inspect API to reflect the fact only a single port is configured by the policy.

Today "fromRules" already has an inbound object we need to check if sectionName works out-of-the-box or requires additional support.
@lobkovilya lobkovilya added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Dec 23, 2024
@lobkovilya lobkovilya added this to the 2.10.x milestone Dec 23, 2024
@Automaat Automaat added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Dec 23, 2024
Automaat added a commit to Automaat/kuma that referenced this issue Jan 22, 2025
@Automaat
feat(kuma-cp): add support for inspect api for new kind Dataplane and…
e890085 
… section name for selecting single inbound

Fixes: kumahq#12361
Signed-off-by: Marcin Skalski <[email protected]>
@Automaat Automaat linked a pull request Jan 22, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
2.10.x
2 participants
@Automaat @lobkovilya