chore(release): v0.1.8

[dray92]

Release v0.1.8 of zxporter, published from the internal services monorepo.

The v0.1.8 tag has already been created and points at this branch's tip — ArgoCD and other tag consumers can use it immediately. This PR is only to advance public main to the released commit for browser convenience.

[gitar-bot]

💡 Security: dcgm-exporter now runs privileged on all providers

Removing the {{- if eq $.Values.global.k8sProvider "gcp"}} gate makes the dcgm-exporter sidecar run with privileged: true unconditionally, so every cluster (not just GCP) now grants the container full host access. The change is intentional and documented (MIG enumeration requirement), but it broadens the security posture for all existing non-GCP installs on upgrade; ensure operators are aware and, if possible, keep it gated behind a values flag (e.g. dcgmExporter.privileged) defaulting appropriately so clusters without MIG can opt out.

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

CI failed: The CI build check failed because generated installer files in the dist/ directory are out of sync with current source templates, requiring a local run of 'make build-installer' and committing the updated bundles.

Overview

1 change-related build failure found across 1 analyzed log. The CI check 'Check if build-installer produces changes' detected uncommitted modifications in the dist/ directory.

Failures

Uncommitted Changes in dist/ Directory (confidence: high)

• Type: build
• Affected jobs: 93262266597
• Related to change: yes
• Root cause: The generated Kubernetes bundle files under dist/ (such as updated security contexts and capabilities for NVML/GPU resource handling) are out of sync with the latest source templates.
• Suggested fix: Run make build-installer locally, review the resulting changes in the dist/ directory, commit them, and push the updated branch.

Summary

• Change-related failures: 1 failure due to out-of-date generated files under dist/
• Infrastructure/flaky failures: 0
• Recommended action: Run make build-installer locally and commit the resulting changes in dist/ before pushing.

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Advances public main to release version v0.1.8 for browser convenience. Consider restricting privileged execution on dcgm-exporter to avoid security escalation across all providers.

💡 Security: dcgm-exporter now runs privileged on all providers

📄 helm-chart/zxporter-nodemon/templates/daemonset.yaml:246-249

Removing the {{- if eq $.Values.global.k8sProvider "gcp"}} gate makes the dcgm-exporter sidecar run with privileged: true unconditionally, so every cluster (not just GCP) now grants the container full host access. The change is intentional and documented (MIG enumeration requirement), but it broadens the security posture for all existing non-GCP installs on upgrade; ensure operators are aware and, if possible, keep it gated behind a values flag (e.g. dcgmExporter.privileged) defaulting appropriately so clusters without MIG can opt out.

🤖 Prompt for agents

Code Review: Advances public main to release version v0.1.8 for browser convenience. Consider restricting privileged execution on dcgm-exporter to avoid security escalation across all providers.

1. 💡 Security: dcgm-exporter now runs privileged on all providers
   Files: helm-chart/zxporter-nodemon/templates/daemonset.yaml:246-249

   Removing the `{{- if eq $.Values.global.k8sProvider "gcp"}}` gate makes the dcgm-exporter sidecar run with `privileged: true` unconditionally, so every cluster (not just GCP) now grants the container full host access. The change is intentional and documented (MIG enumeration requirement), but it broadens the security posture for all existing non-GCP installs on upgrade; ensure operators are aware and, if possible, keep it gated behind a values flag (e.g. dcgmExporter.privileged) defaulting appropriately so clusters without MIG can opt out.

Tip

Comment Gitar fix CI to trigger a fix.

_{Was this helpful? React with 👍 / 👎 | Gitar}