SOC are currently using this tool but it is built on a Windows VM in Azure, they wish to migrate this into AKS for multiple reasons, and have asked us to explore doing so
It's likely that this can be done via self-service by the SOC team, they will need permission to push to flux-config, and access to our AKS clusters - potentially a KT on how flux makes all this work together and some help troubleshooting - To be discussed
Intended Outcome
Vector is installed on required AKS environments with correct settings
DTSPO-22072
Summary
SOC are currently using this tool but it is built on a Windows VM in Azure, they wish to migrate this into AKS for multiple reasons, and have asked us to explore doing so
It's likely that this can be done via self-service by the SOC team, they will need permission to push to flux-config, and access to our AKS clusters - potentially a KT on how flux makes all this work together and some help troubleshooting - To be discussed
Intended Outcome
Vector is installed on required AKS environments with correct settings
Impact on Teams
None