Long Kubernetes URLs (e.g., Rancher-hosted)

Will Hallam — Tue, 06 Sep 2022 20:23:31 GMT

Disclaimer: The tips and tweaks herein come with no support or warranty, explicit or implied. Caveat emptor!

At this writing, discovery of Kubernetes clusters takes some liberties with the provided cluster URL which breaks some implementations, namely those which include a path in the base cluster URL. An example of this is Rancher, which uses a consistent base URL and then adds a path unique to each cluster. Fortunately, this is easily remedied. Here's an example of one way to do so.

Under Pattern Designer->Custom Operations, open record "Kubernetes Get Call"
Locate the line of JavaScript which constructs the URL -- for me it was line 94 and it looked like this:
1. url = protocol + '://' + host + ':' + port + api_prefix;
Comment the original line, then make a copy which reads as follows:
1. url = protocol + '://' + host + ':' + port + path + api_prefix;
Update the record

This change will include any path elements you specify in your pattern URL parameter and allow you to discover individual clusters running under Rancher.

post Long Kubernetes URLs (e.g., Rancher-hosted) in ITOM articles

Long Kubernetes URLs (e.g., Rancher-hosted)