Learn how to configure and integrate a DevOps Intelligence Websocket to accommodate an On-premise proxy adapter to assess cloud resources in your hybrid IT estate.
Some clients have a busines requirement to expose internal on-premise applications to external users, while not making the applications public. Such configurations enable secure access while maintaining control over data and traffic flow within your corporate boundaries. You can bolster security and compliance requirements by keeping sensitive data on premise, not sending it directly to a cloud-based service without compromising service access.
DevOps Intelligence accommodates such circumstances by supporting Websockets, which enable on-premise poxy adapters broadening your service reach without comrpomising security.
Configuring WebSocket
Complete the following procedure to integrate a proxy adapter using a WebSocket:
Create a wsmesh-token:
The wsmesh-token can be generated by DevOps Intelligence directly using the wsmesh Swagger API Page. It can also 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.
Deploying 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.
Adding 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 OnPremise support; the proxy ID will be unique for every supported tool.