v4.7.0
NCTL 4.7.x Release Notes
v4.7.10
Enhancements
- Added ValidatingPolicy support to all scan types.
Bug Fixes
- Fixed incorrect filepath issue for AI remediations.
- Automatically add all required permissions for RBAC policyset to reports-controller when using
nctl add cluster. - CVE fixes
v4.7.9
Updates
- Support for AI auto-remediations for resources present in the cluster.
Bug Fixes
- Fix
nctl scan helm --helpshowing irrelevant flags. - Fix
nctl scan repositorywhen local kubeconfig points to an EKS cluster. For scan repository, kubeconfig should not produce any side effects. - CVE fixes
v4.7.8
Updates
- Improve logging. Use the
klogstyle verbosity logging. - Remove support for
terraform-config(.tf) andterraform-state(.tfstate) extensions from terraform scan. - Remove (old) remediation annotation from scan report results.
Bug Fixes
- Fix file count mismatch for non-k8s files in repository scanning.
- Add more e2e tests for better coverage of
nctl.
v4.7.4
Major Changes
- Using nctl to install Kyverno Operator and Nirmata Kube Controller follow secure-by-default standards (i.e., provide readonly access to resources).
- Removed
nctl installcommand. The recommended installation method for Enterprise Kyverno and Operator is via Helm. nctl scan kubernetesnow include K8s best practices policies out-of-the-box.- Add support for Kyverno 1.14’s ValidatingPolicy in
nctl scan kubernetescommand. - Changes to
nctl logincommand. By default login is for NCH.
Enhancements
- Include cluster name in SARIF reports.
- Remove redundant logs from
nctl scancommand. - Exclude specific files or directories when using
nctl scan repositorycommand. - Support for
--analyzeflag fornctl scan repositorycommand. - Added support for csv as a policy report output format.
- Added severity field in detailed scan reports.
- Support for directories in
nctl scan remediatecommand.