Trial | HeroDevs Docs

Pull and deploy the NES for Ingress NGINX Trial, an unpatched rebuild of the final upstream ingress-nginx release, for integration evaluation

HeroDevs offers a trial version of NES for Ingress NGINX to test the drop-in replacement with your existing clusters, Helm values, and ingress rules before you subscribe. The trial is a HeroDevs rebuild of the upstream ingress-nginx controller at v1.15.1, the final upstream release before end-of-life, built with upstream's Go toolchain, module set, and NGINX base image. It contains no security fixes and is not supported.

DO NOT use the "NES for Ingress NGINX Trial" in production. It is provided solely for integration evaluation and receives no CVE fixes.

No HeroDevs access token is required. Trial images accept any username and password at the registry login.

Pull the image

echo neverendingsupport | docker login registry.nes.herodevs.com -u HeroDevs --password-stdin
docker pull registry.nes.herodevs.com/nes/ingress-nginx:v1.15.1-nes-trial

The image is published for linux/amd64 and linux/arm64.

Deploy with the NES Helm chart

The trial uses the same NES Helm chart as the supported product. Only the image tag and the registry credentials differ.

Create the namespace and an image pull secret

Any username and password work for the trial. Create the namespace where ingress-nginx will run, then create the secret in it:

kubectl create namespace ingress-nginx
kubectl create secret docker-registry herodevs-registry \
  --docker-server=registry.nes.herodevs.com \
  --docker-username=HeroDevs \
  --docker-password=neverendingsupport \
  -n ingress-nginx

Point the chart at the trial image

Add the trial tag and the pull secret to your values file. Your existing ingress rules, annotations, and controller settings carry over unchanged.

controller:
  image:
    registry: registry.nes.herodevs.com
    image: nes/ingress-nginx
    tag: v1.15.1-nes-trial
    digest: ""
imagePullSecrets:
  - name: herodevs-registry

Install or upgrade the release

helm repo add HeroDevs https://neverendingsupport.github.io/helm-charts
helm repo update
helm upgrade --install ingress-nginx HeroDevs/ingress-nginx \
  --namespace ingress-nginx \
  --create-namespace \
  -f values.yaml

To replace an existing upstream ingress-nginx release in place, follow Migrate an existing ingress-nginx Helm release to NES and use the trial tag in place of the NES image tag.

Verify

kubectl get pods -n ingress-nginx
kubectl exec -n ingress-nginx deploy/ingress-nginx-controller -- /nginx-ingress-controller --version

The version output reports v1.15.1-nes-trial. The image also ships a /TRIAL-LICENSE file stating the trial terms.

How the trial differs from NES for Ingress NGINX

	Trial	NES for Ingress NGINX
Image tag	`v1.15.1-nes-trial`	The current NES tag on Helm Charts
Controller source	upstream `controller-v1.15.1`, unmodified	upstream `controller-v1.15.1`, unmodified
CVE fixes	None	Ongoing, per the Support Policy
Go toolchain and modules	Identical to upstream, as of the final upstream release	Kept current by HeroDevs
NGINX base image	Identical to upstream, digest-pinned	HeroDevs `nginx-base` with backported NGINX and OpenSSL fixes
Registry credentials	Any username and password	HeroDevs access token
Support and SLA	None; evaluation only	HeroDevs support and CVE SLA
Production use	Not permitted	Yes

The controller code is identical in both. Everything the supported product adds arrives through the toolchain, dependencies, and base image, so a successful trial deployment is a faithful rehearsal of the supported deployment.

Move to the supported product

To subscribe, contact HeroDevs. Once you have an access token, recreate the pull secret with your contact e-mail and token, set controller.image.tag to the current NES version from Helm Charts, and run helm upgrade. Nothing else in your values changes.