Skip to content

fix(issue): support haproxy external ingress priority detection#465

Open
ybelMekk wants to merge 30 commits into
feat/cve-priorityfrom
fix/external-ingress-class-haproxy
Open

fix(issue): support haproxy external ingress priority detection#465
ybelMekk wants to merge 30 commits into
feat/cve-priorityfrom
fix/external-ingress-class-haproxy

Conversation

@ybelMekk

@ybelMekk ybelMekk commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

What

  • Reuse shared ingress class mapping to detect externally exposed ingresses in issue checker.
  • Include both external-haproxy and external-fa-haproxy as external exposure.
  • Keep unknown or missing ingress classes non-external.

Test

  • go test ./internal/issue/checker/... -count=1

ybelMekk added 25 commits June 15, 2026 10:10
…checker

- Add priorityActNow, priorityHigh, priorityElevated, priorityMonitor fields to ImageVulnerabilitySummary model
- Expose priority fields in vulnerability.graphqls and GraphQL resolvers
- Add VULNERABILITY_PRIORITY_ACT_NOW and VULNERABILITY_PRIORITY_HIGH sort fields
- Add ExternalIngressActNowVulnerabilityIssue type and issue checker
- Map priority signals (EPSS, KEV, ransomware) via VulnerabilityPrioritySignals
- Bump golang.org/x/net to v0.55.0 and golang.org/x/crypto to v0.52.0 to fix known vulnerabilities
- Update v13s/pkg/api to v0.0.0-20260525171357-13563f32226d (priority_elevated, priority_monitor support)
…; fix ExternalIngressActNow resolver stubs; add priority sort fields
@ybelMekk ybelMekk requested a review from Copilot June 17, 2026 08:03
@ybelMekk ybelMekk changed the title fix(issue): support haproxy external ingress detection fix(issue): support haproxy external ingress priority detection Jun 17, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the issue checker’s logic for detecting externally exposed ingresses by reusing the shared ingress class mapping from the workload/application domain, ensuring HAProxy external ingress classes are correctly treated as external exposure.

Changes:

  • Added application.IsIngressClassExternallyExposed to centralize “external exposure” detection (including authenticated external classes).
  • Updated v13s workload issue detection to use the shared mapping instead of a single hardcoded ingress class name.
  • Expanded test coverage and testdata to cover legacy external, external HAProxy, authenticated external HAProxy, and non-external/unknown/missing ingress classes.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
internal/workload/application/ingress_class_mapping.go Adds exported helper to determine whether an ingress class is externally exposed.
internal/issue/checker/workload_v13s.go Switches external ingress detection to use the shared helper (supports HAProxy external classes).
internal/issue/checker/workload_v13s_test.go Parameterizes and expands the external-ingress critical vulnerability test matrix.
internal/issue/checker/testdata/dev-gcp/devteam/apps.yaml Updates/extends test fixtures for various ingress class scenarios.

@ybelMekk ybelMekk marked this pull request as ready for review June 17, 2026 09:07
@ybelMekk ybelMekk requested a review from a team as a code owner June 17, 2026 09:07
@ybelMekk

Copy link
Copy Markdown
Contributor Author

Waiting for #452 to merge first, since this PR is based on that branch and should be merged afterwards.

@ybelMekk ybelMekk force-pushed the feat/cve-priority branch from 4277e04 to fd27b92 Compare June 19, 2026 07:17
@ybelMekk ybelMekk force-pushed the feat/cve-priority branch from 8dc6401 to 7576a8d Compare June 26, 2026 07:40
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.

2 participants