v0.1.0
Changelog
New features:
mkat eks find-role-relationships
now uses a full-fledged IAM policy evaluation engine to determine which pods can assume IAM roles in the account.
Enhancements:
- Add an option to skip EKS hostname checks in
mkat eks find-role-relationships
, when using a non-standard EKS API server hostname (--skip-eks-hostname-check
) - Add an option in
mkat eks find-role-relationships
to specify the EKS cluster name when it cannot be automatically detected from the KubeConfig file (--eks-cluster-name
) - Document permissions needed in AWS and K8s in https://github.com/DataDog/managed-kubernetes-auditing-toolkit/blob/v0.1.0/permissions.md
- Implement better logic to detect when a cluster is an EKS cluster. This used to fail when the EKS API server was using a non-443 port