IAM in Inventory; settings reach pods.
Import AWS IAM + more reliable ZopDay deploys
ZopNight discovery now covers AWS IAM users, groups, roles, and policies alongside cloud resources, searchable on the Inventory page. ZopDay deploys get materially more reliable: Settings values now actually reach running pods, private-registry image pulls work on every cluster including bring-your-own, and the deploy wizard rejects invalid Dockerfiles before submit.
What's in this release
- New ZopNight: import AWS IAM users, groups, roles, and policies into discovery, retaining their role and permission shape and searchable on the Inventory page next to compute and storage (GCP and Azure IAM next)
- Improved ZopDay: Settings values (env vars, replicas, port, liveness path, CPU / memory caps) now reliably apply to the running service instead of being dropped at install
- Improved ZopDay: private-registry image pulls now work on every cluster, including bring-your-own clusters with no cloud identity tied to a registry
- Improved ZopDay: Azure AKS clusters bind the org's default registry at provision time, so the first deployment doesn't fail on an image pull