Multi Spinnaker

The multi-cd audit option is available to add multiple spinnaker instances in ISD spinnaker. By adding multiple instances, you can manage and monitor multiple applications and the pipelines of all the added spinnaker instances. To enable this option you need to set multi_cd_enabled: true in the app config file as shown below:

apiVersion: v1
data:
  app-config.json: |-
    {
        "endPointUrl": "/gate/",
        "setApplicationInterval": 300000,
        "triggerPipeline": false,
        "cdTool": "Spinnaker",
        "multi_cd_enabled": true,
        "hide_accessManagement": true,
        "hide_agent": true,
        "hide_cd_integration": false,
        "hide_cloud_targets": true,
        "hide_integrations": true,
        "hide_pipelineTemplates": true,
        "hide_policies": true,
        "hide_users": true,
        "grafana_enabled": true,
        "grafanaPipelineInsightsEndpoint": "
https://grafana.hyd-qa.opsmx.net/grafana/d/pipeline-insight/pipeinsights
",
        "grafanaStageInsightsEndpoint": "
https://grafana.hyd-qa.opsmx.net/grafana/d/stage-insight/stageinsights
"

When multi spinnaker is enabled, some of the ISD pages such as Access Management, Agents, Cloud Targets, Integrations, Pipeline Templates, Policies and Users are disabled by default.

The following code section must be added in the app config file when enabling multi spinnaker to hide the above mentioned pages.

"hide_accessManagement": true,

"hide_agent": true,

"hide_cd_integration": false,

"hide_cloud_targets": true,

"hide_integrations": true,

"hide_pipelineTemplates": true,

"hide_policies": true,

"hide_users": true,

Once the flag is enabled, go to Setup > CD Integration to add the spinnaker instances.

Click + New CD Integration. The CD Integration details page is displayed.

Enter the required details of the instance and click Save. The CD instance is added. You can add any number of spinnaker instances. Once the instances are added, access the echo-local.yml file.

  • Goto Repo > Default > Profiles > echo-local.yml

  • Provide the name of the CD name in the name field that you have given in ISD and add your rabbitmq ip address in the host field . 

message-broker:
  endpoint:
    name: rabbitmq     #Currently support rabbitmq only
  username: rabbitmq         #rabbitmq username to connect
  password: Networks123      #rabbitmq password to connect
  host: 34.136.9.29    #rabbitmq endpoint to connect
  port: 5672                 #rabbitmq port to connect
ssd:
  name: preview-saas-ssd
  enable: false
spinnaker:
  name: helm4042spin      #Should be same as account name given in spinnaker setup
  extensibility:
    plugins:
      Opsmx.EchoEventPlugin:
        enabled: true
        version: 1.0.1
        config: null

The CD name of the Spinnaker instance in ISD should match to the name field in the echo-local.yml file.

The created spinnaker instances CD Name along with the applications are displayed in the home page.

You can select the required CD instance name from the CD Name drop down.

The multi spinnaker executions, audit, and insights can be viewed by accessing the Audit and Insights pages.

Viewing Audits for Newly added CDs

The audit pages display the various pipeline executions and changes that took place in the CD instances.

To view the pipeline executions for the created multi spinnaker instance and all its applications, navigate to Audit > Pipeline Execution.

The pipeline executions of all the pipelines are displayed.

To view the audit page of the pipelines for the created multi spinnaker instance and all its applications, navigate to Audit > Pipeline Audit.

The pipeline changes for all the pipelines are displayed.

Viewing Insights for Newly added CDs

The insights pages display the usage, pipeline and stage wise details. The pipeline and stage insights pages are disabled by default.

Follow the instructions provided in Enabling Pipeline Insights and Stage Insights in ISD to enable these insights pages in ISD for the multi spinnaker.

To view the Pipeline Insights for the pipelines; navigate to Insights > Pipeline Insights. Select the required CD instance name from the CD Name drop down.

The pipeline insights for the selected instance is displayed.

To view the stage insights of the pipelines; navigate to Insights > Stage Insights. Select the required CD instance name from the CD Name drop down.

The stage insights for the selected instance is displayed.

To view the usage Insights of the pipelines; navigate to Insights > Usage Insights.

This page displays the data from all the configured Spinnakers.

You do not have the option to choose specific instances to be displayed in usage insights. Usage details of all the instances are only displayed.

PreviousConfiguration Changes to Enable / Disable Insights PagesNextAPI Reference

Last updated