Linkerd executable on self hosted Web
322
Linkerd on the self-hosted web
Why Linkerd should be in cloud? The reason is that currently linkerd exists only the CLI form. By encapsulating this in a docker container and providing this as a REST API endpoints, this could be issued from anywhere. The kubeconfig file is to be provided. Ensure that IP address:Port of the server is provided in the kubeconfig. Local/Docker IP should be provided, the one which could be reached by this container
docker-compose.yaml
services:
link-cloud:
image: manjurn/link_cloud
container_name: link-cloud
ports:
- 5000:5000
volumes:
- path/to/kubeconfig/file:/flask/.kube
Commands:
https://host:5000/check - Executes `linkerd check`
https://host:5000/mccheck - Executes `linkerd mc check` meant for Multi-Cluster check
https://host:5000/version - Executes `linkerd version`
Content type
Image
Digest
sha256:32c2fd45f…
Size
63.8 MB
Last updated
almost 3 years ago
docker pull manjurn/link_cloud