-
Notifications
You must be signed in to change notification settings - Fork 16.7k
Conversation
@k8s-bot e2e test this |
@technosophos @michelleN here is the chart that I was saying takes a really long time to install and sometimes causes timeouts. The issue is that it requires multiple job hooks that depend on certain pods to be fully running. The hook jobs do retry and back off but helms' default timeout is not enough for a freshly installed cluster to pull down all of the images and such in time. Is there a way to make sure Helm does not time out while post install hooks are running or furthermore to ensure that post install hooks have their own timeout? |
@viglesiasce great contrib. I've worked with spinnaker in the past and would like to give the review a shot. It's quite the chart... |
In 2.2 there is a |
To install the chart with the release name `my-release`: | ||
|
||
```bash | ||
$ helm install --name my-release stable/spinnaker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mention the timeout value on install
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It won't exist in helm until 2.2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a note for now. Will update when helm 2.2 ships
1. You will need to create 2 port forwarding tunnels in order to access the Spinnaker UI: | ||
export GATE_POD=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "component=gate,app={{ template "fullname" . }}" -o jsonpath="{.items[0].metadata.name}") | ||
export DECK_POD=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "component=deck,app={{ template "fullname" . }}" -o jsonpath="{.items[0].metadata.name}") | ||
kubectl port-forward $GATE_POD 8084 & |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add --namespace {{ .Release.Namespace }}
to both port forwards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done deal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Jenkins Charts e2e failed for commit d67b6be. Full PR test history. cc @viglesiasce The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This installs Spinnaker and its dependencies as well as configures Spinnaker to operate as a deployment engine for the local Kubernetes cluster. It also configures 2 Jenkins jobs for use in the implementation of CI pipelines:
For more info about Spinnaker on Kubernetes, check out:
http://www.spinnaker.io/docs/kubernetes-source-to-prod