Halyard | extremely horizontally scalable Triplestore with support | Database library

This is more or less a guess, since you didn't include one iota of version information about your spinnaker setup, but...

According to at com.netflix.spinnaker.clouddriver.aws.provider.agent.ReservationReportCachingAgent$_determineVpcOnlyAccounts_closure2.doCall(ReservationReportCachingAgent.groovy:117) ~[clouddriver-aws.jar:na] in your gist, which corresponds to getAmazonEC2(credentials, credentials.regions[0].name) in version 6.5.2

it appears they do not tolerate having an empty regions: [] like you do; thus:

Looks as though you either had a problem with network connectivity or some other reason that your system can't reach the host keyserver.ubuntu.com. Make sure you can reach that server (try pinging it for instance) and your install should work.

I've forwarded the port 9000 instead of 8084 and changed the --gate-endpoint http://localhost:9000/gate and it worked.

@Thiago you might have to go an edit .hal/config and modify network: default to network: and followed by hal deploy apply. We ran into same issue, this is a dirty hack that worked for us.

I found a way but it is manually done, working within the spinnaker-spinnaker-halyard container. I'm sure there is a better way...

I add a custom bom as additionalConfigMap to the values.yml file

A probe by the kubelet can end in one of three states:

• successful
• failed (command returned a non-0 exit code)
• errored (command did not return before the timeout elapsed, the command does not exist inside the container, etc)

Here is the code (in 1.10.11) where the event probe errored is recorded. Note that err != nil.

Here is the code that calls the above function - when err != nil (the probe returned an error), the result is discarded.

Only probes that fail will actually cause the pod's ready state to be changed.

While its not documented here, it does look like there is a podAnnations option.

I was able to add the file ~/.hal/default/service-settings/front50.yml with the following config to get kube2iam annotations on the front50 pods.

I was able to resolve this by adding a filter template in the metric of the canary config. The canary analysis task was able to run without error after adding this

Your entrypoint script needs to end with the magic line exec "$@".

In Docker in general, a container startup launches the container entrypoint, passing it the command as parameters. (A Kubernetes pod spec refers to these parts as "command" and "args".) Once the entrypoint completes, the container exits. Since your entrypoint script just runs kubectl config and helm init commands which all complete promptly, the container exits almost immediately; when it does, Kubernetes restarts it; and when it has to restart it more than two or three times, it goes into CrashLoopBackOff state.

The usual way to get around this is to set up the entrypoint script to do any required first-time setup, then exec the command that was passed to it as parameters. Then the command (in your case, /opt/halyard/bin/halyard) winds up being "the main container process", and has the magic process ID 1, and will receive signals at container termination time.

Also note that there is a reasonably standard pattern for accessing the Kubernetes API from a pod that involves configuring a service account for the pod and using an official API, or else launching a kubectl proxy sidecar. You might be able to use that in place of the manual setup steps you have here. (I've never tried to launch Helm from inside a Kubernetes pod, though.)