-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(infrastructure): Bring multiapps-controller
to CF
#2988
Conversation
d69e68e
to
3d7bfca
Compare
92b44f3
to
3a8cfef
Compare
123b53b
to
20cb27a
Compare
20cb27a
to
510b180
Compare
e2fe4ea
to
e416935
Compare
88a853e
to
77e93bc
Compare
2bb85c1
to
b09dacf
Compare
f0381c2
to
3145d06
Compare
…line security group JSON configuration
This reverts commit 6bc4b40.
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are the changes I've added https://github.com/cloudfoundry/app-autoscaler-release/pull/2988/files/06211c4b32b2ede7af2f65c7c4b28ef53b851d0e..bb445946f78f0dd7464f5c0b6f1124f8c53e52b8
I also cleaned up CF and deleted the postgres bosh deployment. After I've cleaned up everything, the deploy-multiapps-controller concourse job ran successfully 🟢
Let's bring this in and start harvesting the fruits of the deploy-service 🧑🌾
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Co-authored-by: Silvestre Zabala <[email protected]> Co-authored-by: geigerj0 <[email protected]>
Motivation
To move autoscaler components into cf for production consumption we need to relay on a app lifecycle solution for autoscaler as a whole.
As a first step we need to set up the multi apps controller in the OSS infrastructure, which has a dependency on a DB solution such as the Postgres DB service.