Thanks to this answer
I fixed this by adding the following to my lftp command
set ftp:use-allo false; set ftp:passive-mode true; set ftp:prefer-epsv false;
which made my finished command the following
lftp -e "set ftp:use-allo false; set ftp:passive-mode true; set ftp:prefer-epsv false; set ssl:verify-certificate no; open mediajackagency.com; user $...
Periodicity will only come into effect if the overall integration and deployment processes take a long time to complete, which is more likely the actual problem. Said differently, in an environment where applications are built using lightweight architectures that are quickly scanned, built, deployed and tested, periodicity would cease to be relevant.
So, I actually ended up with the following strategy.
I separated the charts from the source code. Basically, I have a repository that tracks all the helm charts only
I wanted to have a repository representing my cluster(s) so it's easy to rebuild a cluster from it
I also wanted to keep track of the current version deployed. Basically, this repository ...
It sounds like you are talking about Canary Analysis ? If so, Spinnaker has deployment based on canary analysis built on, using metrics provided by the application telemetry. To quote the Spinnaker docs:
Your application might send performance metrics which are published and available by default. You can also install a monitoring agent to collect more ...