← Back to home
Comparison · Infra & APIs

Greenbone Vulnerability Manager vs HAProxy Kubernetes Ingress Controller

A side-by-side editorial comparison of Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller — release velocity, themes, recent moves, and the top alternatives to consider.

Greenbone Vulnerability Manager vs HAProxy Kubernetes Ingress Controller: at a glance

FeatureGreenbone Vulnerability ManagerHAProxy Kubernetes Ingress Controller
SectorInfra & APIsInfra & APIs
Velocity score5.05.0
Sparks · 30d00
Top themesvulnerability-management, active-directory, reporting, agentsingress-controller, haproxy, kubernetes, patch-release
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is Greenbone Vulnerability Manager?

Greenbone's gvmd starts on Active Directory credentials as report exports settle.

26.43.0 on 27 October adds an LDAP/AD credential type, a GMP command to verify it and feature flags for AD integration, plus encryption and anonymization options for agent bundles. The surrounding releases finish the report export work: cancellation in 26.40.0, then reuse of completed exports and repeatable downloads. 26.41.0 also adds executable report formats and validates keys and certificates when credentials are modified.

Read the full Greenbone Vulnerability Manager trajectory →

What is HAProxy Kubernetes Ingress Controller?

Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies

The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.

Read the full HAProxy Kubernetes Ingress Controller trajectory →

Greenbone Vulnerability Manager vs HAProxy Kubernetes Ingress Controller: editorial side-by-side

G5.0

Greenbone's gvmd starts on Active Directory credentials as report exports settle.

◆ Current state

26.43.0 on 27 October adds an LDAP/AD credential type, a GMP command to verify it and feature flags for AD integration, plus encryption and anonymization options for agent bundles. The surrounding releases finish the report export work: cancellation in 26.40.0, then reuse of completed exports and repeatable downloads. 26.41.0 also adds executable report formats and validates keys and certificates when credentials are modified.

◆ Where it's heading

Report export, the summer's main thread, has reached the fix-and-polish stage. New work is moving toward agents and directory integration: agent OS metadata, group scheduling delay and bundle options sit alongside the AD credential type. The steady memory-leak fixes suggest a code base being tightened as these features land.

◆ Prediction

AD integration sits behind feature flags, so expect follow-up releases to complete it. The entries don't say when it will be enabled by default.

H5.0

Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies

◆ Current state

The controller remains on the 3.2 patch line. Since v3.2.14 the only release of substance is v3.2.15, which stopped filtering ingresses on IngressClass name at ingestion, reworked status publishing and moved to Go 1.27. Later patches are mainly dependency and tooling updates, with v3.2.18 keeping every TLS secret of an ingress on the same host and v3.2.19 fixing a data race on the reload flag.

◆ Where it's heading

The ssl-passthrough theme has faded, and the series is now closer to routine upkeep than stabilization. Fixes have moved to ingress class handling, TLS secret storage and concurrency, with test coverage arriving in the same changes. Patches keep coming, but no new configuration surface has appeared on this line in the entries shown, apart from amending the SSL frontend through a custom resource in v3.2.15.

◆ Prediction

Expect further patches dominated by go.mod and Kubernetes client updates, with new capability waiting for a later line.

Alternatives to Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Greenbone Vulnerability Manager or HAProxy Kubernetes Ingress Controller.

See all Greenbone Vulnerability Manager alternatives → · See all HAProxy Kubernetes Ingress Controller alternatives →

Recent activity from Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoHAProxy Kubernetes Ingress Controllerv3.2.19: reload flag data race fix and x/ package bumps
  2. 5d agoGreenbone Vulnerability Managergvmd 26.43.0: LDAP/AD credentials and agent-bundle encryption
  3. 12d agoHAProxy Kubernetes Ingress Controllerv3.2.18: keeps all TLS secrets per host, CRD panic fix
  4. 17d agoHAProxy Kubernetes Ingress Controllerv3.2.17: k8s.io, x/ and client-native dependency updates
  5. 18d agoGreenbone Vulnerability Managergvmd 26.42.0: Scan config in report XML, export fixes
  6. 20d agoGreenbone Vulnerability Managergvmd 26.41.0: Executable report formats, credential validation
  7. 25d agoHAProxy Kubernetes Ingress Controllerv3.2.16: dependency, CI and test maintenance
  8. 1mo agoGreenbone Vulnerability Managergvmd 26.40.2: Web target and agent error-path fixes
  9. 1mo agoGreenbone Vulnerability Managergvmd 26.40.1: Sensor scanner port handling, leak fixes
  10. 1mo agoGreenbone Vulnerability Managergvmd 26.40.0: Cancel report exports over GMP
  11. 1mo agoHAProxy Kubernetes Ingress Controllerv3.2.15: IngressClass ingestion fix, status rework, Go 1.27
  12. 2mo agoHAProxy Kubernetes Ingress Controllerssl-passthrough allow/deny lists retained on the https frontend

Frequently asked questions

What is the difference between Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller?

They serve adjacent needs but don't currently overlap on shipped themes. Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Greenbone Vulnerability Manager better than HAProxy Kubernetes Ingress Controller?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Greenbone Vulnerability Manager and HAProxy Kubernetes Ingress Controller are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to Greenbone Vulnerability Manager?

Top Greenbone Vulnerability Manager alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Greenbone Vulnerability Manager alternatives" section above for the current picks, or visit /alternatives/greenbone-gvmd for the full list with editorial commentary on each.

What are the best alternatives to HAProxy Kubernetes Ingress Controller?

Top HAProxy Kubernetes Ingress Controller alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "HAProxy Kubernetes Ingress Controller alternatives" section above for the current picks, or visit /alternatives/haproxy-ingress for the full list with editorial commentary on each.