FAQs

Question: What are the ways I could try spinnaker for trial purposes? Answer: You can install your own spinnaker in the following ways:

In a Kubernetes Cluster using helm charts
Standalone on a VM
On AWS via AWS marketplace

Question: How to configure GitLab webhook in Spinnaker? Answer: Steps to configure GitLab Webhook:

Navigate to the settings page of a repository
Choose the 'Integrations Menu'
Fill out the fields
1. URL: The Payload URL should be $API-ENDPOINT/webhooks/webhook/gitlab We need Spinnaker’s API running on an endpoint that is publicly reachable. This is required to allow GitLab’s webhooks to reach Spinnaker. For example, http://<Public-IP>:8084/webhooks/webhook/gitlab If you’re unsure of what your Spinnaker API endpoint is, check the value of services.gate.baseUrl in ~/.hal/$DEPLOYMENT/staging/spinnaker.yml. The value of $DEPLOYMENT is typically default.
2. Secret Token: Spinnaker validates the source of the requests with the secret token
Select 'Trigger' options like, "Push Events", "Tag Push Events" etc.
Check / Un-check "Enable SSL verification" according to Spinnaker Server SSL Configuration
Click "Add Webhook"

Question: How to access Spinnaker with External(or Halyard IP) after installing as Distributed installation on kubernetes ? Answer: After Spinnaker installation is done, we need to change the Service type for deck and gate to LoadBalancer IP and override the UI and gate base URL's hal config security ui edit \ --override-base-url http://<deck-IP>:9000/ hal config security api edit \ --override-base-url http://<Gate-IP>:8084/ Question: How to customize the spinnaker pipeline to ignore the failed steps and proceed with exception to next steps? Answer: We have to enable a checkbox in the pipeline execution options in Spinnaker. After login to Spinnaker console, click on Pipelines, then clink on any stage option, under execution option you can see how spinnaker should handle a failure of the stage. Refer the screenshot below.

Question: Spinnaker pipeline shows running even after all the tasks are completed. What can we do? Answer: One possible solution is to clear the Redis Cache.

Question: How to remove local debian installation? Answer: Uninstalling Halyard deletes the entire contents of your ~/.hal directory.

If you used Halyard to deploy Spinnaker, and you want to purge that deployment, run the following command: hal deploy clean
Now you can safely uninstall Halyard: # ~/.hal/uninstall.sh

echo host: 0.0.0.0 > /home/spinnaker/.hal/default/service-settings/gate.yml

echo host: 0.0.0.0 > /home/spinnaker/.hal/default/service-settings/deck.yml These links may help:

GRANT ALL PRIVILEGES ON . TO 'orca'@'%';

GRANT ALL ON . TO 'orca'@'%' IDENTIFIED BY '<OrcaDBPassword>' WITH GRANT OPTION;

GRANT ALL ON . TO 'orca_migrate'@'%' IDENTIFIED BY '<OrcaUserPassword-1>' WITH GRANT OPTION;

GRANT ALL ON . TO 'orca_service'@'%' IDENTIFIED BY '<OrcaUserPassword-2>' WITH GRANT OPTION;

flush privileges;

or a fairly simple procedure here:

$ hal config version edit --version (xxxx)(Desired version)

$ hal deploy apply (edited)

Example:

$hal config version edit --version "1.16.1"

$hal deploy apply Question: How to configure email notifications in spinnaker? Answer: This may help to setup email notifications

There are many other interesting videos at:

First try to restart halyard "sudo service halyard restart" and, if it still doesn't come up...
Check for the status of the halyard "sudo service halyard status".
If it shows inactive then try to start again "sudo service halyard restart"
In case if the service doesn't respond with above #1 & #2, try "sudo update-halyard"

Question: Which version of Kubernetes Supports fine with Spinnaker? Answer: In theory, Spinnaker should with any of the supported versions of Kubernetes.

Clouddriver is responsible to connect with kubernetes and it uses kubectl binary to do so (V2 version). So, as the current version of kubectl of 1.16, Kubernetes versions up to 1.18 should work fine. Note that, if using halyard, one must use a relatively newer version of Halyard for for deployments to work as apps/v1beta2 has been depricated in Kubernetes 1.16. Given a choice, we recommend k8s 1.15 with Spinnaker 1.17.6 Question: How to bake helm3 chart in Spinnaker? Answer: The following link gives step-by-step instructions:

echo "host: 0.0.0.0" | tee \

~/.hal/default/service-settings/gate.yml \

~/.hal/default/service-settings/deck.yml

sudo hal deploy apply

Here is a referenced link it will help

Here is a steps to connect using port forwarding,

Local machine to Spinnaker.

Step1: -> Localhost to AWS instance

ssh -A -L 9000:localhost:9000 -L 8084:localhost:8084 -L 8087:localhost:8087 ec2-user@<aws-instance-ip>

Step2: -> Aws instance to Spinnaker cluster

You Also need to change the timezone in the UI's by using settings.js file. Question: Can Spinnaker use local Storage ? Answer: The Spinnaker microservice responsible for persisting your pipeline configs and application metadata,front50, has support for the storage systems you listed. One could add support for additional systems like mysql by extending front50, but that support does not exist today.By configuring front50 to use s3 and pointing it at a minio installation. Question: How to setup Spinnaker with restricted namespace access? Answer: You can try to get your admin to give you access to a ClusterRole+RoleBinding that has access to namespaces read.

Something like this:

ClusterRole apiVersion: rbac.authorization.k8s.io/v1 metadata: name: namespace-reader rules: - apiGroups: [""] resources: ["namespaces"] verbs: ["get", "watch", "list"] --- kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1 metadata: name: read-all-namespaces subjects: - kind: User name: your-user apiGroup: rbac.authorization.k8s.io roleRef: kind: ClusterRole name: namespace-reader apiGroup: rbac.authorization.k8s.io Question: How to setup Spinnaker communicate with kubernetes cluster? Answer: Try to adding the kubernetes details to the halyard contest

hal config provider kubernetes account add <ACCOUNT> hal config provider kubernetes enable

Here is a reference link

hal config provider kubernetes account edit ACCOUNT --live-manifest-calls=true Question: What is the relationship between projects and application in spinnaker? Answer: Projects provide an aggregated view of a collection of applications, but that's about it. If you're only interested in a subset of applications managed by Spinnaker, it's a decent way to manage them.

The relationship is modeled as many-to-many: a project is made up of one or more applications, and applications can be part of multiple projects.

Being in a project doesn't affect the application in any way, beyond making it present in the project view. There are no notifications to be configured at the project level,

or pipelines that span multiple applications. You can set up a project pretty quickly and easily to get an idea what the view looks like. Question: How to deploy distributes spinnaker under specific namespace? Answer: Hal command is

hal config deploy edit \

--type distributed \

--account-name offline-k8s \

Below snippet is example:

~/.hal/default/profiles/gate-local.yml

server: tomcat: protocolHeader: X-Forwarded-Proto remoteIpHeader: X-Forwarded-For internalProxies: .*

After all the Changes need to do spinnaker deploy again. Question: How to take Backup and Restore spinnaker Pipelines? Answer: You Can copy the configurations for pipelines and applications from front50 manually,

For pipelines, just do a curl to:

curl http://<front50-IP>:8080/pipelines -o pipelines.json

For application config:

curl http://<front50-IP>:8080/v2/applications -o applications.json

To push pipeline config to Spinnaker:

cat pipelines.json | curl -d@- -X POST \ --header "Content-Type: application/json" --header \ "Accept: /" http://<Front50_URL>:8080/pipelines Question: How to specify an elastic beanstalk deployment using spinnaker? Answer: You can deploy to Beanstalk by using the Jenkins stage and then deploy a Cloud-formation template with the CF stage,Basically you just have to set up the AWSprovider as per below instructions

It is possible to change that configuration and refresh it at runtime, but it would involve editing the on-disk yaml file that backs the Clouddriver component of Spinnaker and triggering the /config-refresh endpoint. Question: How to create service account for spinnaker? Answer: Create Role for spinnaker with role name spinnaker-role you can edit role as per you need,

apiVersion: rbac.authorization.k8s.io/v1

kind: Role

metadata:

name: spinnaker-role

namespace: default

rules:

- apiGroups: [""]

resources: ["namespaces", "configmaps", "events", "replicationcontrollers", "serviceaccounts", "pods/logs"]

verbs: ["get", "list"]

- apiGroups: [""]

resources: ["pods", "services", "secrets"]

verbs: ["*"]

- apiGroups: ["autoscaling"]

resources: ["horizontalpodautoscalers"]

verbs: ["list", "get"]

- apiGroups: [“apps”]

resources: [“controllerrevisions”, "statefulsets"]

verbs: [“list”]

- apiGroups: ["extensions", "app"]

resources: ["deployments", "replicasets", "ingresses"]

verbs: ["*"]

Service Account for spinnaker:

apiVersion: v1 kind: ServiceAccount metadata: name: spinnaker-service-account namespace: default

Main part roll binding:

apiVersion: rbac.authorization.k8s.io/v1

kind: RoleBinding metadata: name: spinnaker-role-binding namespace: default roleRef: apiGroup: rbac.authorization.k8s.io kind: Role name: spinnaker-role subjects: - namespace: default kind: ServiceAccount name: spinnaker-service-account Question: How to trigger a Spinnaker pipeline by schedule or time? Answer: When editing your pipeline, click "Add Trigger" and then choose "CRON" as the trigger type. There is a tooltip on the "CRON Expression" field that gives some help on how to construct the cron expression. Question: How to access spinnaker from my Machine's IP Answer: 1) Edit /etc/apache/ports.conf and remove change Listen 127.0.0.1:9000 to Listen 9000

2)Add a reverse proxy for ports you wish to open in Apache

2)Edit the pipeline config and under the Deploy stage edit the appropriate "Deploy Configuration". Select the load balancer use a Spring Expression like:${ trigger.properties.LB_NAME }

This assumes you have pre-provisioned a loadbalancer that matches the LB_NAME passed in the trigger properties file. Question: Where to modify Spinnaker to listed on network ip,Rather that localhost? Answer: Add a config in /opt/spinnaker/config/gate.yml

Cors: allowedOriginsPattern: 'http://your ip address:9000'

then restart the gate sudo restart gate Question: How to Decide which stage to go next in spinnaker ? Answer: In the desired pipeline select Stage A > Execution Options > If stage fails > ignore the failure

Stage B > Execution Options > Conditional on Expression > Add your expression when successful

Stage C > Execution Options > Conditional on Expression > Add your expression when Stage A fails. Question: Using the k8s Job stage, we can execute anything e.g. aws cli commands. But what if we don't have a k8s account available? How do we execute aws cli as part of a pipeline? Answer: One option is to use Jenkins job, shell script as part of Jenkins pipeline stage and use it from Spinnaker Jenkins stage

Could also use custom stage with a webhook service that will run the script as built in or passed as argument Question: Can I re-run a failed stage in Spinnaker? Answer: Yes, you can re-run a failed stage in Spinnaker from the "Execution Details" view of a failed stage - under the Actions menu, there will be a menu item to restart the stage again.

Question: Can I notify people when a manual judgement stage is waiting for their action? Answer: Yes, the manual judgement stage has a different notification option from other stages in its configuration setting to allow to do this. This allows you to notify people via email, chat and other supported notification options when a manual judgement stage is waiting their inputs.

This issue occurs mostly in the Kubernetes version 1.19.x or the latest version. If you run into this issue in the hal config file under "omitKind" add "podPrest" in the below format omitKinds: - "podPreset" Generic
Now, restart spinnaker services hal deploy apply Generic
Once, all the spinnaker services are up and running all the deployed resources should be visible in Spinnaker Clusters. Question: How do we get of a pipeline-cancel situation? It keeps going round-and-round but does not come back? Answer: a) Please delete the underlying objects in k8s/deployment envrionment. For example, if we were trying to create a "deployment", go and delete it. That should fix the issue. That object, if it is crashloop, will not go away easily. A simple approach is to have pipelines that delete objects created by other pipelines...so you can simple run a pipeline to clean-up a deployment left in a messy state. b) orca pod could have run out of resources. Try restarting it or increasing its CPU/Mem. Question: All spinnaker pipelines have vanished. What should we do? Answer: Try restarting the spin-front50 pod.

PreviousX.509 NextGlossary

Last updated 2 years ago

Was this helpful?