everything is bash ( a lot of non standard tools ).tests and looping are done via jq ( validating json schema ).i am using json file to define projects.Of course it does not exist, currently I am using bunch of scripts, buts its not so good. validate projects -> if contains specific files.to timeout if command/taks is taking more than X seconds.
Pritunl gravitational code#
Pritunl gravitational update#
In the coming few months, AWS Fargate will update the LATEST flag to Platform Version (PV) 1.4.0. Subject: AWS Fargate Platform Version LATEST Flag Update The other option i think i’m most likely to implement because it’s fast and easy is just using a separate deployment in the same cluster and weighted dns to serve some small percentage of traffic to a canary deployment and continuously deploy there first. i suspect armory is above what i’m able to pay for a saas-type solution, and with limited time to focus on this specifically, flagger ( service mesh) and spinnaker ( learning curve/setup/maintenance?) i suspect is just overkill. Some of the options i’ve considered ( from cncf landscape) are flagger ( requires service mesh) and spinnaker ( gold standard? heavy weight). we use kubernetes and some folks use a service mesh, but not all, and we don’t always use the same clusters for various reasons.
what do you guys use for continuous delivery/continuous integration/continuous release? i work at a smallish (~100 people) company and we’re generally jamming pretty hard on delivering product features instead of focusing on infrastructure.