hal command: hal deploy apply how can i use it offline? - spinnaker

I used halyard version 0.42.0-20180302093153 and Spinnaker version 1.6.0.
Is there any way that makes me to use hal command: hal deploy apply offline ?

Although there was no ability to do this when you asked your question, there's been work on this since then, under https://github.com/spinnaker/spinnaker/issues/2640. Presumably at some point this will get officially released and the documentation will be updated accordingly, but as of today it appears to be in a "coming, but not here yet" state.

Related

How can I create a testing environment for a project in gcp compute engine?

I am working on a project on GCP. It is a website that is live. It is running on a compute engine based on Ubuntu Linux. The problem I am trying to solve is how to create a live testing environment. Here is the flow of thoughts:
I have the live version that is working fine
I then create a feature that I want to deploy to the live version
But before deploying it, I want to test if the project will still work fine without errors on GCP.
Therefore, I want to find a way of deploying the test version of the project on gcp, and access it live, without tampering with the old version
Both of them need to be running live on GCP, so that I can see the contrast between the standard live version and the testing version
I have not tried anything yet. I am confused on where to start. I have checked out some proposed solutions online: Terraform and Docker mainly. But then I don't know how to go about it.
My expectation is that if I go to live-working-url.com, I get the stable working version of the project. Then be able to set up something like testing.live-url.com and see the test version. Both of these should be coming from the GCP compute engine.
Also, if there are other thoughts and ideas on how to work with testing in GCP, please share, they are highly appreciated
Thank you.

"One or more of the requested capabilities are not supported." AWS FARGATE

I'm getting "One or more of the requested capabilities are not supported." error when trying to mount a volume from Amazon EFS on AWS FARGATE.
Edit your service and update "Platform version" to 1.4.0
You can do this in terraform by adding an optional variable platform_version to the aws_ecs_service resource
Here is the official AWS communication about the platform version 1.4.0
Here is an important quote:
The primer blog post goes into more detail about the philosophy behind why we introduced Fargate platform versions and, for example, the practical reasons why we are not tagging platform version 1.4.0 as LATEST just yet.
The primer blog post is here. Keep the focus on this "critical" point:
Starting with the introduction of this platform version (1.4.0), we will hold on moving the LATEST tag. We want to provide a runway for users that use LATEST as an additional precaution. This means that if you are deploying today using the tag LATEST to identify a Fargate platform version, the system will keep referencing platform version 1.3.0 for now (albeit, technically, the latest platform version available today is 1.4.0).
These users could either start experimenting with 1.4.0 by explicitly deploying to it or wait until we move the tag LATEST to point to platform version 1.4.0. [Updated on 6/17/2020] We plan to make this change in the May 2020 time frame We plan to make this change at some point in Q3/2020, thus giving customers [Updated on 6/17/2020] about a month a few months to test 1.4.0 before it gets tagged as LATEST. Expect a formal announcement for this change.
This is intended to give users a window of time to test 1.4.0 without being forced to use it if they use the tag LATEST. We do not anticipate disruption but we decided to be conservative.
That's why you should use, at the time of writing, version 1.4.0, instead of LATEST in order to use AWS EFS.

Enable ChaosMonkey in Spinnaker

I've installed Spinnaker on AWS using https://aws.amazon.com/quickstart/architecture/spinnaker/
I've also installed Halyard and updated Spinnaker to 1.5.0
Problem is after I execute
hal config features edit --chaos true
The option for ChaosMonkey doesn't appear in the UI.
I've restarted the service and rebooted the system, I've also tried to manually change the setting in any settings.js files of Deck , but to no avail.
What am I missing ?
There is a guide here for getting chaos monkey up-and-running on GCE with hal. I realize it's not a perfect answer, but maybe it will point out a platform independent step you might have missed?

Jaeger standalone without docker

Cannot find any information if Jaeger can be executed without docker?
Does a standalone jar exist, or will there be a release in the future for Jaeger like Zipkin has ?
The Downloads page (https://www.jaegertracing.io/download/) lists both the Docker images and the raw binaries built for various platforms (Linux, macOS, windows). You can also build binaries from source.
Just to add to Yuris answer, you can also download the source from github - Github - Jaeger This is useful for diagnosing issues, or just getting a better understanding of how it all works.
I have run both the released apps and custom versions on both windows and linux servers without issues. For windows I would recommend running as a service using Nssm. Nssm details

Spinnaker: Delete old AMIs after successful deployment

Is there a native Spinnaker way to cleanup old AMIs after a successful deployment took place?
It's nice that the previous version of the newest deployment is available in AWS but the previous ones keep adding-up and thus incur not only cost but also confusion.
Thanks.
Nothing native in Spinnaker. Janitor Monkey will do this, however, and cleans up a bunch of other unused AWS artifacts.
It's very possible Spinnaker will support this natively in the future - just not right now.