Closed tcourtnage-tbl closed 1 year ago
Thank you! This was due to a simple typo and will be fixed in the 2.2.4 release.
If you'd like to resolve it for your local module before release, you can replace Public\kubernetes-protection.ps1
with the following file:
Update file using PowerShell 5.1 on Windows:
(Invoke-WebRequest -Uri https://raw.githubusercontent.com/CrowdStrike/psfalcon/8aa75a140e4647e21a9234c3147d7d5bbcc606cb/Public/kubernetes-protection.ps1 -UseBasicParsing).Content > $HOME\Documents\WindowsPowerShell\Modules\PSFalcon\2.2.3\Public\kubernetes-protection.ps1
Update file using PowerShell Core on Windows:
(Invoke-WebRequest -Uri https://raw.githubusercontent.com/CrowdStrike/psfalcon/8aa75a140e4647e21a9234c3147d7d5bbcc606cb/Public/kubernetes-protection.ps1 -UseBasicParsing).Content > $HOME\Documents\PowerShell\Modules\PSFalcon\2.2.3\Public\kubernetes-protection.ps1
Update file using PowerShell Core on Linux/Mac:
(Invoke-WebRequest -Uri https://raw.githubusercontent.com/CrowdStrike/psfalcon/8aa75a140e4647e21a9234c3147d7d5bbcc606cb/Public/kubernetes-protection.ps1 -UseBasicParsing).Content > $HOME/.local/share/PowerShell/Modules/PSFalcon/2.2.3/Public/kubernetes-protection.ps1
Solved in v2.2.4 release.
The
Get-FalconContainerCluster
function does not return any results. Running it with-Verbose
seems to indicate it's not attempting to do anything at all. Using cURL to same route (/kubernetes-protection/entities/kubernetes/clusters/v1
) shows the correct results, and falconpy works as well. I had a coworker confirm the behaviour as well.To Reproduce
Request-FalconToken -ClientId '<client_id>' -ClientSecret '<client_secret>'
)Test-FalconToken
)Get-FalconContainerCluster
function.Expected behavior I expect to see a list of our EKS clusters, but no results are returned. As mentioned, cURLing the same endpoint shows the proper results.
Environment (please complete the following information):
Transcript content