NGINX Ingress Controller vs. SUSE NeuVector

Best suited if we have to manage external traffic inside your Kubernetes cluster and want to use granular control to your applications.

Incentivized

Invited by TrustRadius (TR) on Vendor's Behalf

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

SUSE NeuVector is exceptional when you want to make your Kubernetes cluster secure. You can limit network connections, scan containers, container registries and Kubernetes nodes for vulnerable software, forbid running specific commands on certain or all containers. You can enable security for individual containers - when SUSE NeuVector has learned container specifics. That's why you can deploy SUSE NeuVector on production Kubernetes clusters where you are already running conteiners - it will not break anything.

• Provide access to containers
• Manage traffic
• Route traffic
• Lightweight
• Near to zero downtime

Incentivized

Invited by TrustRadius (TR) on Vendor's Behalf

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info

• Scans containers software for known vulnerabilities
• Denies command execution in containers
• Prevents unwanted network connections from/to containers

• Its not related to Ingress functionality but certificate management with cloud vendor would be a feature i would like to see.

Incentivized

Invited by TrustRadius (TR) on Vendor's Behalf

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• I like everything about NeuVector. They are on the right development path.

We are already using NGINX which is so reliable, it definitely lends weight to our decision to select NGINX Ingress Controller. Also, even though it is a little more complex to manage, NGINX Ingress Controller definitely have a richer feature set, better performance, caching, traffic management among other features which was why it was chosen.

Incentivized

Invited by TrustRadius (TR) on Vendor's Behalf

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. TR verified that a representative sample of customers was invited. More Info

SUSE NeuVector is deployed on your Kubernetes, and data does not leave your data center. Sysdig is a cloud platform - you have no full control over what happens with your data. Also, SUSE NeuVector has a capability to prevent specific command execution ir containers, but Sysdig does not have such ability. Sysdig is not an open-source solution, but SUSE NeuVector is.

• Security is one of the best objective which we achieve with NGINX Ingress
• Cost optimization is one of the business objective

Incentivized

Invited by TrustRadius (TR) on Vendor's Behalf

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• We went from being blind to what happens in the Kubernetes network to seeing everything and being able to control Kubernetes network communications.
• Now we are able to detect vulnerable containers faster.