SUSE NeuVector 5.0 preview3 is now available for testing, + EOL of registry.neuvector.com

[NeuVector Updates for new release and security updates for the NeuVector container security platform]

Hello,
You are receiving this email because you are a member of the NeuVector Technical Updates mailing list. To unsubscribe or manage your subscription please go to https://lists.suse.com/mailman/listinfo/neuvector-updates

SUSE NeuVector v5.0 (Open Source) preview3 Available for Testing

  *   Preview3 version can be pulled from Docker Hub
  *   Adds SLE vulnerability scanning for run-time (containers, nodes etc). Registry/image scanning already supported in preview2
  *   Offers first views of new features such as Zero-drift process protection, Split mode protection for Network and Process, WAF rules, CRD for WAF, DLP and Admission Controls, RKE2 support and more! See the preview3 release notes<https://open-docs.neuvector.com/releasenotes/5x> for more details.
  *   The source code on github/neuvector/ has been updated to preview3 accordingly. Reminder: build tools are not yet available but are scheduled to be made available in May.
  *   Documentation at https://open-docs.neuvector.com is in the process of being updated for new features.
  *   The General Availability (GA) of the 5.0 version is currently targeted for May, 2022.

NeuVector Private Registry registry.neuvector.com to be EOL October 1, 2022
The NeuVector images are now available on Docker Hub as publicly available and can be pulled without credentials. This includes the latest 4.x (closed source) as well as 5.x (open source) images. It is no longer required to access the NeuVector customer portal at console.cloud.neuvector.com to retrieve credentials in order to pull images. The private registry registry.neuvector.com will be retired on October 1, 2022 and will no longer support image pulls for the NeuVector images. In order to transition to pulling from Docker Hub:

  *   Change image registry to docker.io
  *   Change image paths from ‘registry.neuvector.com/’ to ‘neuvector/’ and use appropriate image names and tags. Check image names for manager, controller, enforcer, scanner, updater (or allinone if using)
  *   Remove the regsecret for registry.neuvector.com as login is no longer required.
  *   If needed, allow access to docker.io through corporate firewalls
  *   Update Helm chart to the latest, which supports both options, and make sure registry is docker.io and image paths start with ‘neuvector/’
  *   If needed, check any automated scripts that were pulling from registry.neuvector.com and update to docker.io

Enterprise customers of NeuVector can contact support at neuvector.com<mailto:support at neuvector.com> for any questions.

Best regards,
The SUSE NeuVector team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.suse.com/pipermail/neuvector-updates/attachments/20220329/3474626b/attachment.htm>