This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
Constraints not met when deploying CDK #1123
Labels
Comments
|
The bundleplacer code is pulling the constraints from I'm not sure what metadata is supposed to be being passed in or why the constraints from the service definition in the bundle would be ignored. |
adam-stokes
pushed a commit
to Ubuntu-Solutions-Engineering/bundle-placement
that referenced
this issue
Aug 30, 2017
Fixes conjure-up/conjure-up#1123 Signed-off-by: Adam Stokes <battlemidget@users.noreply.github.com>
adam-stokes
pushed a commit
that referenced
this issue
Aug 30, 2017
Fixes #1123 Signed-off-by: Adam Stokes <battlemidget@users.noreply.github.com>
johnsca
pushed a commit
that referenced
this issue
Aug 30, 2017
Fixes #1123 Signed-off-by: Adam Stokes <battlemidget@users.noreply.github.com>
|
@simonklb building now https://code.launchpad.net/~conjure-up/+snap/conjure-up/+build/74806 should be available once thats done |
|
@simonklb can you let us know if this did resolve the issue for you? |
|
@battlemidget confirmed fixed! 👍 thanks guys |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When deploying CDK to AWS I should, by default, end up with three worker nodes that are larger than the rest. This is the case when I'm using
juju deploybut withconjure-upthe worker nodes are the same instance type as the rest.The text was updated successfully, but these errors were encountered: