Route Registrar Changes broke Stratos Functionality

[benjaminguttmann-avtq]

Subject of the issue

With the changes in v14.0.0 the registered routes for the app-autoscaler have been changed. The Autoscaler-Api no longer registers with autoscaler.((system_domain)) but with app-autoscaler.((system_domain)). Unfortunately, the value within stratos is hardcoded which means the app-autoscaler use within Stratos is not working anymore right now. Not sure if anything can be done on your side (maybe add the old route to be registered as well) but wanted to make it at least visible. I created an issue in Cloudfoundry Community Stratos Repo as well.

Your environment

• Version of app-autoscaler-release: v14.0.0
• Specify the database PostgreSQL 15.x along-with it's version
• How did you deploy the release?
  • Is your manifest based on app-autoscaler.yml? - Yes
  • Which, if any, ops-files did you apply?
• How did you run the acceptance-tests? - None
  • If you did not run them, please consider running them and attaching the output as well.

Steps to reproduce

Tell us how to reproduce this issue.

Expected behaviour

Tell us what should happen.

Actual behaviour

Tell us what happens instead.

[silvestre]

Hi @benjaminguttmann-avtq ,

the route is set in https://github.com/cloudfoundry/app-autoscaler-release/blame/912cbd185e60e5099342d723d5a242dbb07d5451/templates/app-autoscaler.yml#L296 and the line is there since the start of this file.

I see that the old (deleted) deployment manifest did hardcode it to autoscaler while the new one set its to the variable ((deployment_name)).

We can think about switching the default to hardocde again autoscaler but we currently depend on the fact that we can deploy app-autoscaler-release multiple times in the same foundation for our CI, so we would need to introduce an operations file restoring the current behavior in order not to break our CI.