Hand-maintained — mirrors Chart.yaml version: bumps. See the
GitHub Releases page for the published artifacts.
v1.3.2 — 2026-05-19
Ship values.schema.json at the chart root.
- Helm now validates
--set/-foverrides against the schema on
install and upgrade — typos and wrong-type values fail loudly
instead of rendering quietly bad manifests. - Artifact Hub renders the schema as an interactive Values
schema tab on the listing.
The schema covers every key the chart actually exposes (image,
workload, hpa, enrollment, networking, persistence, proxy, bind,
etc.) with enum constraints on enrollment.mode, networking.mode,workload.type, and image.pullPolicy. resources and affinity
stay permissive (pass-through to Kubernetes types).
v1.3.1 — 2026-05-18
Flip enrollment.api.cleanupOnDelete to default off. The Netskope
API refuses to delete a Publisher with Private Apps attached, so the
1.3.0 default of true could silently fail on scale-down — leaving
orphan Publisher records and stranded app assignments to chase. The
hook is still available; you just have to opt in (cleanupOnDelete: true) and confirm that your auto-scaled replicas never carry app
assignments.
If you’re already on 1.3.0, the new release also pulls in the
slimmed example values and the AH-aligned install path from the
1.1.1 docs work.
v1.3.0 — 2026-05-18
Autoscaling and orphan-Publisher cleanup.
- HorizontalPodAutoscaler template for the StatefulSet path.
CPU-based, autoscaling/v2 API. Enable withhpa.enabled=trueand
tunehpa.minReplicas/hpa.maxReplicas/hpa.targetCPUUtilizationPercentage. Optionalhpa.behavior
block for scale-up/scale-down policies. Silently ignored whenworkload.type=daemonset. - Pod preStop hook in API mode that deletes the tenant-side
Publisher record on every pod termination (HPA scale-down,helm uninstall, node drain). Best-effort: failures do not
block termination, so a network glitch or expired token just
leaves the record for manual cleanup. Disable withenrollment.api.cleanupOnDelete=false.
See autoscaling
for the full setup.
v1.2.0 — 2026-05-18
securityContext, hostNetwork, and dnsPolicy are no longer
exposed as values keys. The chart now derives all three fromnetworking.mode:
networking.mode: pod (default) |
networking.mode: host |
|
|---|---|---|
securityContext |
privileged: false, NET_ADMIN, NET_RAW, runAsUser: 0 |
privileged: true, NET_ADMIN, NET_RAW, runAsUser: 0 |
hostNetwork |
false |
true |
dnsPolicy |
ClusterFirst |
ClusterFirstWithHostNet |
Previously securityContext was overridable via values, but only
in host mode — pod mode silently hardcoded its own block. That
asymmetry made values.yaml look like it ran the Publisher
privileged even in pod mode (which it doesn’t). The new design
makes the helper authoritative for both modes, and values.yaml
honest.
Upgrade hazard: if your values file overrode securityContext,hostNetwork, or dnsPolicy, those overrides are now silently
ignored. Remove them and switch networking.mode instead.
v1.1.1 — 2026-05-18
Docs-only release so Artifact Hub picks up the new README.
- README leads with the Artifact Hub install path
(helm repo add npa … && helm install npa/kubernetes-netskope-publisher)
instead of the local-clone path; local-clone install becomes a
developer footnote. - Slimmed example values to only the keys that aren’t covered by
1.1.0 defaults (pod networking, tunDevice, persistence: false, and
IPv6-disable are all default now). - Replaced every remaining local-path install/upgrade example in the
deep-dive sections so the advice stays consistent end-to-end. - Fixed a stale clone URL in the k3s setup section.
release.ymlnow also fires onREADME.mdchanges so future
README updates ship to Artifact Hub on the next push.
v1.1.0 — 2026-05-18
Defaults overhaul. Values surface unchanged — only defaults moved.
networking.modedefaults topod(washost). Together
with this, the defaulthostNetworkflips tofalseanddnsPolicytoClusterFirst. This makes the out-of-the-box install
work on EKS / AKS / GKE / OpenShift without privileged-host-network
exemptions. Upgrade hazard for existing 1.0.x installs — if
you’ve been running host-mode and haven’t pinnednetworking.mode,
set it explicitly in your values beforehelm upgrade.serviceAccount.createdefaults tofalse. The chart makes no
Kubernetes API calls; the namespace’s default ServiceAccount is
sufficient. Re-enable creation if you want to attach IRSA, Workload
Identity, or per-SA imagePullSecrets.- Memory resources bumped —
limits.memory1Gi→1536Mi,requests.memory384Mi→1024Mi. CPU unchanged. - Removed the dead
livenessProbe:/readinessProbe:value
blocks. They were never read — the DaemonSet/StatefulSet template
hardcodesexecprobes that check the publisher process plus its
on-disk state. Probes are not parameterisable today. - Annotated
securityContext,hostNetwork, anddnsPolicyinvalues.yamlto make explicit that they only take effect innetworking.mode: host.
v1.0.1 — 2026-05-18
- Switch chart icon to the Pages-hosted favicon (the previous Netskope
CDN URL had 404’d). No functional change.
v1.0.0 — 2026-05-18
- Initial public release of the Helm chart.
- DaemonSet and StatefulSet workload modes.
- API enrollment (
enrollment.mode: api) and token enrollment. networking.mode: host(legacy) andnetworking.mode: pod(default
for new clusters).- Optional persistence via PVC.
- BIND9 in-pod forwarder with configurable upstream resolvers.
- Optional egress proxy support.
- Optional
customSettingsConfigMap override ofsettings.json.