[Question] which cluster-autoscaler version is AKS using?

[NissesSenap]

Having issues with the cluster-autoscaler and trying to open an issue upstream.
But I'm unable to provide them with the version since I can't see which version I'm using.

I guess one way could be to look through the logs but It would be nice to see in the portal or at least the documentation.

But for now using kubernetes 1.22 which version of the cluster-autoscaler is in use?

[ghost]

Hi NissesSenap, AKS bot here 👋
Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such:

1. If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster.
2. Please abide by the AKS repo Guidelines and Code of Conduct.
3. If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics?
4. Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS.
5. Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue.
6. If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

[NissesSenap]

Relates to: kubernetes/autoscaler#4923

[NissesSenap]

If any one can enlighten me how I possibly could find the version through the logs that would be awesome.

AzureDiagnostics
| where Category == "cluster-autoscaler"

Gives lots of data but it's not like it says version in each log line so I guess I would have to find the information during the startup and who knows when that was...

[ghost]

Triage required from @Azure/aks-pm

[ghost]

Action required from @Azure/aks-pm

[raghulmsft]

@NissesSenap Thanks for sharing this with us. I am a PM with the AKS portal team and will look into this and get back to you!

[gandhipr]

Pertaining to CA logs - currently, we don't print Cluster Autoscaler version in CA logs. Thanks for sharing and we'll add the CA version log line.

[NissesSenap]

Just a thought it's probably not worth having on each row @gandhipr. I think documenting a query that can be used to gather the version would be a good workaround after you have added the version at the initial startup.

[gandhipr]

Planning on getting one at the start-up, not for all the rows.
using some sort of string matching will help us getting the version.

[palma21]

Seems we're diverging a bit from the actual issue though, if you have any issues with the AKS-managed autoscaler you can just open a support ticket and we'll take it from there.
Having it done in upstream won't automatically fix it in AKS for example.

[ghost]

Hi there 👋 AKS bot here. This issue has been tagged as needing a support request so that the AKS support and engineering teams have a look into this particular cluster/issue.

Follow the steps here to create a support ticket for Azure Kubernetes Service and the cluster discussed in this issue.

Please do mention this issue in the case description so our teams can coordinate to help you.

Thank you!

[ghost]

Case being worked with Microsoft Support, adding stale label for automatic closure if not other reports are added.

[NissesSenap]

@palma21 the upstream issue is already solved. But it's a good thing showing the version of the auto scaler no matter what. That is why I created two issues.
The other issues are linked to this issue as well. You will see that if you look at the history of this issue.

[ghost]

Case being worked with Microsoft Support, adding stale label for automatic closure if not other reports are added.

[ghost]

This issue will now be closed because it hasn't had any activity for 7 days after stale. NissesSenap feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.