Prisma Cloud Compute: Defender was not identifying the correct kubernetes version
592
Created On 03/24/25 21:11 PM - Last Modified 04/24/26 17:19 PM
Symptom
Users have lost visibility into their kubernetes version from Prisma Cloud Compute console.
Environment
- Prisma Cloud Compute Edition
- Defender v32.05.124
- EKS v1.32 or above
Cause
- The issue was previously fixed in version 30.02.
- Due to a regression issue which caused this defect reoccurred in version 32.05.
Resolution
- The issue is resolved in version 33.01.137 or higher.
- Upgrade to version 33.01.137 or higher by downloading a new yaml file or helm chart from the console.
- This will cause the correct kubernetes version to get detected as mentioned.