You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the primary machine is created via Clusters-Keeper, it passes a bunch of text via the EC2 User-Data field.
This field is limited to 16KB which is too small for what we use it for.
Currently that field contains a bash script which:
pre-pulls images
runs custom script as defined in PRIMARY_EC2_INSTANCES_ALLOWED_TYPES for the primary machine type
create a docker swarm
transmits a docker-compose file
start a docker-compose file with a bunch of ENV variables + among other WORKERS_EC2_INSTANCES_ALLOWED_TYPES which is typically huge
All in all the complete resulting text file is > 16KB and that is not sustainable.
The content you are editing has changed. Please copy your edits and refresh the page.
The new AMI allows to only call a pre-baked script that takes care of most of the work. only the pre-pull images have to be transfered, thus reducing the size by a huge amount.
In need even the docker-compose files could be pre-baked.
When the primary machine is created via Clusters-Keeper, it passes a bunch of text via the EC2 User-Data field.
This field is limited to 16KB which is too small for what we use it for.
Currently that field contains a bash script which:
All in all the complete resulting text file is > 16KB and that is not sustainable.
Tasks
The text was updated successfully, but these errors were encountered: