Learn how to configure and integrate a DevOps Intelligence Websocket to accommodate an OnPremise Proxy Adapter to assess cloud resources in your hybrid IT estate.
WebSocket configuration:
Complete the following procedure to integrate a proxy adapter using WebSocket
Create a wsmesh-token:
The wsmesh-token can be generated DevOps Intelligencerectly using the wsmesh Swagger API Page or can be generated in the following two ways:
{ "broker": "mcmp:devops-intelligence:service", "name": "name of the token", "single_use": false }
Please make sure wsmesh service is enabled for the tenant
Create a UUID for the Proxy Adapter
Generate a UUID using the Version 1 UUID Generator found at the Online UUID Generator Web site. This ID will be the proxy id used to identify the proxy adapter for the KMOA Console OnPrem instance.
Deploy a generic Proxy Adapter using Helm Chart
Complete the following procedure to deploy a generic proxy adapter:
Download a Generic Proxy Pod Image from the file server. The file_server Swagger can be accessed in two ways:
Core is deployed on the environment:
Launch Kyndryl applications
Select the
User
icon on the top right corner.
Select
Developer Console
.
In the API Documentation section, select: DevOps Intelligence as Application and file-server as Service.
Core is not deployed on the environment:
Launch the Kyndryl Modern Operations Applications
Select the
Menu
icon
Select
DevOps Intelligence
. Click on
Settings & Utilities
and then,
API Explorer
.
Select
FileServer
from the drop-down menu.
Download the proxy adapter image using the API below:
{ "broker": "mcmp:devops-intelligence:service", "name": "name of the token", "single_use": false}
Add Repo by using the command:
helm repo add devops-intelligence https:
Replace
file-server-token
with the token generated on the previous step
Add the values below in fe-proxy-adapter-helm/-generic-proxy-adapter/values.yaml
HOST: KMOA UI tenant Host URL (e.g.kyndryl.multicloud-ibm.com) WS_TOKEN_NAME: Token Name (Created in step 1) WS_TOKEN: Token (Created in step 1) PROXY_ID: Unique id for the proxy adapter (Created in step 2) WS_adapter: true PROTOCOL: tower APPLICATION: Application Name
Request paramenters: { "broker": "mcmp:devops-intelligence:service", "name": "name of the token", "single_use": false}
Add Repo by using the command:
helm repo add devops-intelligence https:
Replace
file-server-token
with the token generated on the previous step
Add the values below in fe-proxy-adapter-helm/-generic-proxy-adapter/values.yaml:
HOST: KMOA UI tenant Host URL (e.g.kyndryl.multicloud-ibm.com) WS_TOKEN_NAME: Token Name (Created in step 1) WS_TOKEN: Token (Created in step 1) PROXY_ID: Unique id for the proxy adapter (Created in step 2) WS_adapter: true PROTOCOL: tower APPLICATION: Application Name
Install Helm Chart
For Helm Version: 3x.x helm install <<releasename>> devops-intelligence/generic-proxy-adapter -f values.yaml --namespace <<namespace>> --create-namespace Deployment should be successful without any issues.
Add credentials for specific DevOps tools using Proxy ID
The Following DevOps intelligence tools are supported now:
Ansible
ArgoCD
Azure DevOps
GitLab
Github
Jfrog
JIRA (Server Oauth support)
JIRA (Cloud Oauth support)
ServiceNow
SonarQube
In the tools credentials page, add the Proxy ID created in the
Create a UUID for the Proxy Adapter
step for On-Premise support; the Proxy ID will be unique for every supported tool.