webMethods API Control Plane enables centralized platform to manage API Mangement products. It offers functionalities to make decisions based on the performance metrics and patterns. Repository hosting tutorials, code samples, OpenAPI specification files and postman collections.
License: Apache License 2.0
Is this a dummy text? If now: What are the five items?
APIs, Runtime and Data Planes come in varying orders in the Control Plane. It would be nicer if they would also be shown in the same order (easier to understand and use).
RedHat does not support docker or docker-compose. RHEL has a "compatible" product called 'podman' and 'podman' compose. Successfully using MSR leveraging podman and podman-compose. I currently have api control plane running on Windows. Now need to have the api control plane running on RHEL.
When running the podman-compose --- I get the follwing:
podman-compose -f control-plane.yaml up -d
podman-compose version: 1.0.6
['podman', '--version', '']
using podman version: 4.6.1
** excluding: set()
['podman', 'ps', '--filter', 'label=io.podman.compose.project=docker', '-a', '--format', '{{ index .Labels "io.podman.compose.config-hash"}}']
podman volume inspect docker_nginx-certs || podman volume create docker_nginx-certs
['podman', 'volume', 'inspect', 'docker_nginx-certs']
podman volume inspect docker_conf.d || podman volume create docker_conf.d
['podman', 'volume', 'inspect', 'docker_conf.d']
['podman', 'network', 'exists', 'softwareag-api-management']
Traceback (most recent call last):
File "/home/enowak/.local/bin/podman-compose", line 8, in
sys.exit(main())
File "/home/enowak/.local/lib/python3.6/site-packages/podman_compose.py", line 2941, in main
podman_compose.run()
File "/home/enowak/.local/lib/python3.6/site-packages/podman_compose.py", line 1423, in run
cmd(self, args)
File "/home/enowak/.local/lib/python3.6/site-packages/podman_compose.py", line 1754, in wrapped
return func(*args, **kw)
File "/home/enowak/.local/lib/python3.6/site-packages/podman_compose.py", line 2067, in compose_up
podman_args = container_to_args(compose, cnt, detached=args.detach)
File "/home/enowak/.local/lib/python3.6/site-packages/podman_compose.py", line 999, in container_to_args
raise ValueError("'CMD_SHELL' takes a single string after it")
ValueError: 'CMD_SHELL' takes a single string after it
The Status view shows weird values as "Current". What is this column supposed to show? In any case, 53y 7M 13d cannot be correct.
In the documentation, list all the valid options for:
Setting
Setting
Why not do an IP Address lookup to determine what the actual location is? And have an override if necessary.
Configuring API Control Plane with an API-Gateway. According to the documentation:
https://documentation.softwareag.com/wco/11.0.0/en/webhelp/wco-webhelp/#page/wco-webhelp%2Fta-connect_apigw_installer_apicp.html%23
The way to connect to the Control Plane is to edit the custom_wrapper.conf
wrapper.java.additional.306=-Dapigw_cp_agentConfig_enabled=true
wrapper.java.additional.307=-Dapigw_cp_agentConfig_runtimeConfig_runtimeName=demo-props
wrapper.java.additional.308=-Dapigw_cp_agentConfig_controlPlaneConfig_controlPlaneURL=http://localhost:81/
wrapper.java.additional.309=-Dapigw_cp_agentConfig_controlPlaneConfig_username=
wrapper.java.additional.310=-Dapigw_cp_agentConfig_controlPlaneConfig_password=
wrapper.java.additional.311=-Dapigw_cp_agentConfig_runtimeConfig_description="My test description"
Please update the documentation to state:
After successful login, I get the following error while running docker-compose -f control-plane-beta.yaml up -d
Pulling ingress (ghcr.io/softwareag/webmethods-api-control-plane/ingress:latest)...
ERROR: denied
I have defined icons (Azure logo) for all my runtimes in the Control Plane UI. Looks nice! But when I restart the API Gateways and they register again, the Control Plane forgets about the logos.
I am running API Gateway 10.15.0.7.266 on Azure Kubernetes Services (AKS) deployed using Helm charts with the image from containers.softwareag.com. I have added the following configuration for the Control Plane agent:
cp-agent.yml:
----
enabled: true
runtimeConfig:
runtimeName: "API_Gateway_THES_CONFIG"
deploymentType: "PRIVATE_CLOUD"
description: "A demo deployment of SAG API Gateway CONFIG environment"
heartBeatIntervalInSeconds: 30
metricsSynchIntervalInSeconds: 30
assetSynchIntervalInSeconds: 30
region: "azure-westeurope"
location: "Hamburg"
host: "http://config-apigateway-ui.azuredemo-softwareag.com/"
tags:
- thes-demo
- config
capacity:
value: 1000
units: "per second"
controlPlaneConfig:
controlPlaneURL: "https://presalesdemos.apicp-az-eu.webmethods.io"
username: "[email protected]"
password: "***"
But the API Gateway does not show up in the Control Plane. In server.log, I found the following NullPointerException:
2023-08-14 16:27:17 GMT [YAI.0015.8889I] (tid=297) [default][azure-demo-apigateway-78d78df5bd-rjc6r] Control plane agent not configured with environment properties.So trying to read from file.
2023-08-14 16:27:17 GMT [YAI.0005.9999E] (tid=297) Control plane Agent startup failed with exception:: java.lang.NullPointerException
com.softwareag.controlplane.agent.core.configuration.AllSourcesConfigurationProvider.isControlPlaneAgentConfigured(AllSourcesConfigurationProvider.java:81)
com.softwareag.controlplane.agent.core.init.Agent.start(Agent.java:30)
com.softwareag.controlplane.agent.apigateway.impl.RuntimeAPIGatewayDataProvider.initializeAgent(RuntimeAPIGatewayDataProvider.java:29)
com.softwareag.apigateway.is.init.ISPackageManager.startup(ISPackageManager.java:218)
apigateway.startup(apigateway.java:57)
...
PFA the full server.log file.
I also tried with just the mandatory parameters:
cp-agent.yml:
----
enabled: true
runtimeConfig:
runtimeName: "API_Gateway_THES_CONFIG"
# deploymentType: "PRIVATE_CLOUD"
# description: "A demo deployment of SAG API Gateway CONFIG environment"
# heartBeatIntervalInSeconds: 30
# metricsSynchIntervalInSeconds: 30
# assetSynchIntervalInSeconds: 30
# region: "azure-westeurope"
# location: "Hamburg"
# host: "http://config-apigateway-ui.azuredemo-softwareag.com/"
# tags:
# - thes-demo
# - config
# capacity:
# value: 1000
# units: "per second"
controlPlaneConfig:
controlPlaneURL: "https://presalesdemos.apicp-az-eu.webmethods.io"
username: "[email protected]"
password: "***"
Same result. What am I doing wrong? How can I increase the log level for the agent? Maybe the user does not have enough rights in the Control Plane?
In trace mode, the log does not reveal much more:
2023-08-14 18:30:30 GMT [YAI.0015.8887D] (tid=296) [default][azure-demo-apigateway-78d78df5bd-m7qkr] Debug: ---------Starting Control plane Agent startup-------
2023-08-14 18:30:30 GMT [YAI.0015.8887D] (tid=296) [default][azure-demo-apigateway-78d78df5bd-m7qkr] Debug: Not Configuration provider set. Using AllSourcesConfigurationProvider by default
2023-08-14 18:30:30 GMT [YAI.0015.8889I] (tid=296) [default][azure-demo-apigateway-78d78df5bd-m7qkr] Control plane agent not configured with environment properties.So trying to read from file.
2023-08-14 18:30:30 GMT [YAI.0015.8887D] (tid=296) [default][azure-demo-apigateway-78d78df5bd-m7qkr] Debug: Reading from YAML file.Executing YAMLConfigurationSource
2023-08-14 18:30:30 GMT [YAI.0015.8887D] (tid=296) [default][azure-demo-apigateway-78d78df5bd-m7qkr] Debug: Reading Control plane agent configuration from:/opt/softwareag/IntegrationServer/instances/default/packages/WmAPIGateway/resources/configuration/cp-agent.yml
2023-08-14 18:30:30 GMT [YAI.0005.9999E] (tid=296) Control plane Agent startup failed with exception:: java.lang.NullPointerException
com.softwareag.controlplane.agent.core.configuration.AllSourcesConfigurationProvider.isControlPlaneAgentConfigured(AllSourcesConfigurationProvider.java:81)
com.softwareag.controlplane.agent.core.init.Agent.start(Agent.java:30)
com.softwareag.controlplane.agent.apigateway.impl.RuntimeAPIGatewayDataProvider.initializeAgent(RuntimeAPIGatewayDataProvider.java:29)
com.softwareag.apigateway.is.init.ISPackageManager.startup(ISPackageManager.java:218)
apigateway.startup(apigateway.java:57)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:566)
com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:405)
com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:761)
com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:67)
com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
com.wm.app.b2b.server.ACLManager.process(ACLManager.java:339)
com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:33)
com.wm.app.b2b.server.invoke.ConcurrentRequestLimitProcessor.process(ConcurrentRequestLimitProcessor.java:57)
com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:400)
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:631)
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:436)
com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:394)
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:260)
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:116)
com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:75)
com.wm.app.b2b.server.SessionInvoke.run(SessionInvoke.java:30)
com.wm.util.pool.PooledThread.run(PooledThread.java:127)
java.base/java.lang.Thread.run(Thread.java:829)
{1}
Thanks! Best regards,
Thomas
Hi,
Found a minor documentation issue in Github.
I see version number mismatch between Github note and formal product documentation on minimum API Gateway version needed to integrate API Control plane v11.
For API Gateway, Github note calls out as 10.15.0.8, where as formal documentation as 10.15.0.10.
To align with formal documentation I think it would be nice if you update Github documentation note with 10.15.0.10 as .env and values.yaml files refers v11 of API Control plane images .
On Manage data planes and on Manage APIs, you can filter by status, but not on Manage runtimes:
The Manage runtimes view should show the owner name instead of a cryptic ID.
The activities view seems to be ordered in chronological order with oldest first. The view would be much more helpful if it were ordered the other way around, with latest first.
You cannot tell versions apart:
Only when you open the twister, the view will display the version number:
I get the following error (after describing the control-plane pods) when trying to deploy API Control Plane on my system using Helm. Please suggest what needs to be done. Feel free to ask for specifications. Thanks.
kubectl describe pods --namespace control-plane
Name: assetcatalog-57f5575d78-pcdhn
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:44:48 +0530
Labels: app=assetcatalog
date=1710760402
pod-template-hash=57f5575d78
Annotations:
Status: Running
IP: 10.1.0.182
IPs:
IP: 10.1.0.182
Controlled By: ReplicaSet/assetcatalog-57f5575d78
Containers:
assetcatalog:
Container ID: docker://b7444fdb9b029d3cb0f4bd6ba7457b2e1920ca31c90022135ab2aade7d97c121
Image: sagcr.azurecr.io/controlplane-assetcatalog:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-assetcatalog@sha256:8f85d6734bc6c0083cca961c22781c0da6e4bdfb4339d432f6e5c1deeb8e35a0
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:50:58 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 18 Mar 2024 16:49:25 +0530
Finished: Mon, 18 Mar 2024 16:50:55 +0530
Ready: False
Restart Count: 4
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/assetcatalog/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/assetcatalog/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
assetcatalog-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 8m59s default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Normal Scheduled 7m43s default-scheduler Successfully assigned control-plane/assetcatalog-57f5575d78-pcdhn to docker-desktop
Normal Pulled 7m38s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 2.451s (2.452s including waiting)
Normal Pulled 6m3s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 2.102s (2.102s including waiting)
Warning Unhealthy 5m3s (x3 over 6m34s) kubelet Readiness probe failed: Get "http://10.1.0.182:8080/api/assetcatalog/health/readiness": dial tcp 10.1.0.182:8080: connect: connection refused
Normal Pulled 4m29s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 1.995s (1.995s including waiting)
Warning BackOff 3m23s (x4 over 4m48s) kubelet Back-off restarting failed container assetcatalog in pod assetcatalog-57f5575d78-pcdhn_control-plane(45e53e79-0e93-497f-afd6-911307400fc3)
Normal Pulling 3m9s (x4 over 7m40s) kubelet Pulling image "sagcr.azurecr.io/controlplane-assetcatalog:11.0"
Normal Pulled 3m7s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 2.154s (2.154s including waiting)
Normal Created 3m6s (x4 over 7m37s) kubelet Created container assetcatalog
Normal Started 3m6s (x4 over 7m37s) kubelet Started container assetcatalog
Warning Unhealthy 2m3s (x3 over 6m23s) kubelet Liveness probe failed: Get "http://10.1.0.182:8080/api/assetcatalog/health/liveness": dial tcp 10.1.0.182:8080: connect: connection refused
Name: assetcatalog-75cbc56d7c-nbvvt
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:31:05 +0530
Labels: app=assetcatalog
date=1710759663
pod-template-hash=75cbc56d7c
Annotations:
Status: Running
IP: 10.1.0.177
IPs:
IP: 10.1.0.177
Controlled By: ReplicaSet/assetcatalog-75cbc56d7c
Containers:
assetcatalog:
Container ID: docker://bfdbb0a0505d4c6e47111db52b2ccaf94690a988a402c5bb752d60e7d0639b18
Image: sagcr.azurecr.io/controlplane-assetcatalog:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-assetcatalog@sha256:8f85d6734bc6c0083cca961c22781c0da6e4bdfb4339d432f6e5c1deeb8e35a0
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:51:37 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 18 Mar 2024 16:45:10 +0530
Finished: Mon, 18 Mar 2024 16:46:24 +0530
Ready: False
Restart Count: 7
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/assetcatalog/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/assetcatalog/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
assetcatalog-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 21m default-scheduler Successfully assigned control-plane/assetcatalog-75cbc56d7c-nbvvt to docker-desktop
Normal Pulled 21m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 1.838s (5.89s including waiting)
Normal Pulled 19m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 2.379s (2.38s including waiting)
Normal Killing 18m kubelet Container assetcatalog failed liveness probe, will be restarted
Normal Pulling 17m (x3 over 21m) kubelet Pulling image "sagcr.azurecr.io/controlplane-assetcatalog:11.0"
Normal Pulled 17m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-assetcatalog:11.0" in 3.405s (3.406s including waiting)
Normal Created 17m (x3 over 21m) kubelet Created container assetcatalog
Normal Started 17m (x3 over 21m) kubelet Started container assetcatalog
Warning Unhealthy 16m (x8 over 20m) kubelet Readiness probe failed: Get "http://10.1.0.177:8080/api/assetcatalog/health/readiness": dial tcp 10.1.0.177:8080: connect: connection refused
Warning Unhealthy 10m (x10 over 20m) kubelet Liveness probe failed: Get "http://10.1.0.177:8080/api/assetcatalog/health/liveness": dial tcp 10.1.0.177:8080: connect: connection refused
Warning BackOff 71s (x42 over 14m) kubelet Back-off restarting failed container assetcatalog in pod assetcatalog-75cbc56d7c-nbvvt_control-plane(2ecdce98-f4b9-40be-95b7-ec24825bfb1a)
Name: assetcatalog-7687468cf5-2x6r5
Namespace: control-plane
Priority: 0
Service Account: default
Node:
Labels: app=assetcatalog
date=1710760456
pod-template-hash=7687468cf5
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/assetcatalog-7687468cf5
Containers:
assetcatalog:
Image: sagcr.azurecr.io/controlplane-assetcatalog:11.0
Port: 8080/TCP
Host Port: 0/TCP
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/assetcatalog/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/assetcatalog/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
assetcatalog-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
PodScheduled False
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 2m11s (x5 over 8m12s) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Name: elasticsearch-0
Namespace: control-plane
Priority: 0
Service Account: default
Node:
Labels: app=elasticsearch
apps.kubernetes.io/pod-index=0
controller-revision-hash=elasticsearch-58bd5c8d9c
statefulset.kubernetes.io/pod-name=elasticsearch-0
Annotations: sensor.falcon-system.crowdstrike.com/injection: disabled
Status: Pending
IP:
IPs:
Controlled By: StatefulSet/elasticsearch
Init Containers:
init-sysctl:
Image: public.ecr.aws/docker/library/busybox:latest
Port:
Host Port:
Command:
sysctl
-w
vm.max_map_count=262144
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xk4pr (ro)
Containers:
elasticsearch:
Image: docker.elastic.co/elasticsearch/elasticsearch:8.1.1
Ports: 9200/TCP, 9300/TCP
Host Ports: 0/TCP, 0/TCP
Limits:
cpu: 1
memory: 2Gi
Requests:
cpu: 1
memory: 2Gi
Readiness: http-get http://:9200/_cluster/health%3Flocal=true delay=20s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
elasticsearch-config ConfigMap Optional: false
Environment:
node.name: elasticsearch-0 (v1:metadata.name)
Mounts:
/usr/share/elasticsearch/data from elasticsearch-data (rw)
/usr/share/elasticsearch/logs from logs (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xk4pr (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
elasticsearch-data:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: elasticsearch-data-elasticsearch-0
ReadOnly: false
logs:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
SizeLimit:
kube-api-access-xk4pr:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 21m default-scheduler 0/1 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Warning FailedScheduling 2m11s (x7 over 21m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Name: engine-59d758d49c-ptrbw
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:31:05 +0530
Labels: app=engine
date=1710759663
pod-template-hash=59d758d49c
Annotations:
Status: Running
IP: 10.1.0.175
IPs:
IP: 10.1.0.175
Controlled By: ReplicaSet/engine-59d758d49c
Containers:
engine:
Container ID: docker://ad0dc937d816561e708fdea914938741d821842169814e831f001cd96aa45b44
Image: sagcr.azurecr.io/controlplane-engine:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-engine@sha256:ed7f2e1f5d59f7806e35c80cb6cfba87f94f89ff0fcf099a4ae75604e1e3ea90
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:50:20 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 18 Mar 2024 16:45:39 +0530
Finished: Mon, 18 Mar 2024 16:47:29 +0530
Ready: False
Restart Count: 7
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/engine/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/engine/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
engine-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 21m default-scheduler Successfully assigned control-plane/engine-59d758d49c-ptrbw to docker-desktop
Normal Pulled 21m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-engine:11.0" in 2.144s (11.932s including waiting)
Normal Killing 19m kubelet Container engine failed liveness probe, will be restarted
Normal Pulled 18m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-engine:11.0" in 3.757s (11.272s including waiting)
Normal Created 18m (x2 over 21m) kubelet Created container engine
Normal Started 18m (x2 over 21m) kubelet Started container engine
Normal Pulling 16m (x3 over 21m) kubelet Pulling image "sagcr.azurecr.io/controlplane-engine:11.0"
Warning Unhealthy 10m (x27 over 20m) kubelet Readiness probe failed: Get "http://10.1.0.175:8080/api/engine/health/readiness": dial tcp 10.1.0.175:8080: connect: connection refused
Warning Unhealthy 67s (x22 over 20m) kubelet Liveness probe failed: Get "http://10.1.0.175:8080/api/engine/health/liveness": dial tcp 10.1.0.175:8080: connect: connection refused
Name: engine-7667bd658-rgn9f
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:44:52 +0530
Labels: app=engine
date=1710760402
pod-template-hash=7667bd658
Annotations:
Status: Running
IP: 10.1.0.183
IPs:
IP: 10.1.0.183
Controlled By: ReplicaSet/engine-7667bd658
Containers:
engine:
Container ID: docker://ca6e6e26e3c10a05959703c50da2ebf953ddaf6736929eb1f42cb5c3c295799a
Image: sagcr.azurecr.io/controlplane-engine:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-engine@sha256:ed7f2e1f5d59f7806e35c80cb6cfba87f94f89ff0fcf099a4ae75604e1e3ea90
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:50:47 +0530
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Mon, 18 Mar 2024 16:48:55 +0530
Finished: Mon, 18 Mar 2024 16:50:43 +0530
Ready: False
Restart Count: 3
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/engine/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/engine/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
engine-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 7m44s (x2 over 9m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Normal Scheduled 7m40s default-scheduler Successfully assigned control-plane/engine-7667bd658-rgn9f to docker-desktop
Normal Pulled 7m37s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-engine:11.0" in 1.815s (1.815s including waiting)
Normal Killing 5m40s kubelet Container engine failed liveness probe, will be restarted
Normal Created 5m14s (x2 over 7m36s) kubelet Created container engine
Normal Pulled 5m14s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-engine:11.0" in 2.133s (2.133s including waiting)
Normal Started 5m13s (x2 over 7m36s) kubelet Started container engine
Normal Pulling 3m40s (x3 over 7m38s) kubelet Pulling image "sagcr.azurecr.io/controlplane-engine:11.0"
Warning Unhealthy 3m40s (x5 over 6m20s) kubelet Liveness probe failed: Get "http://10.1.0.183:8080/api/engine/health/liveness": dial tcp 10.1.0.183:8080: connect: connection refused
Normal Pulled 3m37s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-engine:11.0" in 2.138s (2.138s including waiting)
Warning Unhealthy 2m31s (x10 over 6m20s) kubelet Readiness probe failed: Get "http://10.1.0.183:8080/api/engine/health/readiness": dial tcp 10.1.0.183:8080: connect: connection refused
Name: engine-dc5dd4bf5-kgb5s
Namespace: control-plane
Priority: 0
Service Account: default
Node:
Labels: app=engine
date=1710760456
pod-template-hash=dc5dd4bf5
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/engine-dc5dd4bf5
Containers:
engine:
Image: sagcr.azurecr.io/controlplane-engine:11.0
Port: 8080/TCP
Host Port: 0/TCP
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/api/engine/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/api/engine/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
engine-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
PodScheduled False
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 2m11s (x5 over 8m12s) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Name: ingress-579c65d7c4-jbvbm
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:44:56 +0530
Labels: app=ingress
date=1710760402
pod-template-hash=579c65d7c4
Annotations:
Status: Running
IP: 10.1.0.185
IPs:
IP: 10.1.0.185
Controlled By: ReplicaSet/ingress-579c65d7c4
Containers:
ingress:
Container ID: docker://c6d3634fd7ed885d6ef9ba0ad70da8a89c6ecc2f344077f6126b8d9bc99d0351
Image: sagcr.azurecr.io/controlplane-ingress:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-ingress@sha256:170a53cf022d8295d3ffe28bb796f26b4c826a213a3c7349111c9aba1f8ab685
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:52:10 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 18 Mar 2024 16:49:22 +0530
Finished: Mon, 18 Mar 2024 16:52:07 +0530
Ready: False
Restart Count: 3
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 500m
memory: 1Gi
Liveness: http-get https://:8443/api/ingress/health/liveness delay=100s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get https://:8443/api/ingress/health/readiness delay=100s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ingress-config ConfigMap Optional: false
Environment:
Mounts:
/home/license from license-file (rw)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
license-file:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: ingress-config
Optional: false
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 7m40s (x3 over 9m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Normal Scheduled 7m36s default-scheduler Successfully assigned control-plane/ingress-579c65d7c4-jbvbm to docker-desktop
Normal Pulled 7m29s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ingress:11.0" in 2s (4.091s including waiting)
Warning Unhealthy 5m2s kubelet Readiness probe failed: Get "https://10.1.0.185:8443/api/ingress/health/readiness": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Normal Killing 4m56s kubelet Container ingress failed liveness probe, will be restarted
Normal Pulled 4m51s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ingress:11.0" in 1.978s (1.978s including waiting)
Normal Pulling 3m12s (x3 over 7m33s) kubelet Pulling image "sagcr.azurecr.io/controlplane-ingress:11.0"
Normal Created 3m10s (x3 over 7m29s) kubelet Created container ingress
Normal Started 3m10s (x3 over 7m28s) kubelet Started container ingress
Normal Pulled 3m10s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ingress:11.0" in 1.971s (1.971s including waiting)
Warning Unhealthy 56s (x7 over 5m36s) kubelet Readiness probe failed: Get "https://10.1.0.185:8443/api/ingress/health/readiness": dial tcp 10.1.0.185:8443: connect: connection refused
Warning Unhealthy 56s (x5 over 5m36s) kubelet Liveness probe failed: Get "https://10.1.0.185:8443/api/ingress/health/liveness": dial tcp 10.1.0.185:8443: connect: connection refused
Name: ingress-59ccd8cdff-58kwz
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:31:05 +0530
Labels: app=ingress
date=1710759663
pod-template-hash=59ccd8cdff
Annotations:
Status: Running
IP: 10.1.0.174
IPs:
IP: 10.1.0.174
Controlled By: ReplicaSet/ingress-59ccd8cdff
Containers:
ingress:
Container ID: docker://eb28fab4d5838357309418501cd6326b2a0e09d7644985b8d3a5ef70279cb2ca
Image: sagcr.azurecr.io/controlplane-ingress:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-ingress@sha256:170a53cf022d8295d3ffe28bb796f26b4c826a213a3c7349111c9aba1f8ab685
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:52:08 +0530
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Mon, 18 Mar 2024 16:49:27 +0530
Finished: Mon, 18 Mar 2024 16:52:04 +0530
Ready: False
Restart Count: 7
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 500m
memory: 1Gi
Liveness: http-get https://:8443/api/ingress/health/liveness delay=100s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get https://:8443/api/ingress/health/readiness delay=100s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ingress-config ConfigMap Optional: false
Environment:
Mounts:
/home/license from license-file (rw)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
license-file:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: ingress-config
Optional: false
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 21m default-scheduler Successfully assigned control-plane/ingress-59ccd8cdff-58kwz to docker-desktop
Normal Pulled 21m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ingress:11.0" in 1.863s (9.788s including waiting)
Normal Pulling 18m (x2 over 21m) kubelet Pulling image "sagcr.azurecr.io/controlplane-ingress:11.0"
Normal Pulled 18m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ingress:11.0" in 4.226s (6.733s including waiting)
Normal Created 18m (x2 over 21m) kubelet Created container ingress
Normal Started 18m (x2 over 21m) kubelet Started container ingress
Normal Killing 15m (x2 over 18m) kubelet Container ingress failed liveness probe, will be restarted
Warning Unhealthy 10m (x18 over 19m) kubelet Readiness probe failed: Get "https://10.1.0.174:8443/api/ingress/health/readiness": dial tcp 10.1.0.174:8443: connect: connection refused
Warning Unhealthy 68s (x17 over 19m) kubelet Liveness probe failed: Get "https://10.1.0.174:8443/api/ingress/health/liveness": dial tcp 10.1.0.174:8443: connect: connection refused
Name: ingress-d949986fc-hx5rp
Namespace: control-plane
Priority: 0
Service Account: default
Node:
Labels: app=ingress
date=1710760456
pod-template-hash=d949986fc
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/ingress-d949986fc
Containers:
ingress:
Image: sagcr.azurecr.io/controlplane-ingress:11.0
Port: 8080/TCP
Host Port: 0/TCP
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 500m
memory: 1Gi
Liveness: http-get https://:8443/api/ingress/health/liveness delay=100s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get https://:8443/api/ingress/health/readiness delay=100s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ingress-config ConfigMap Optional: false
Environment:
Mounts:
/home/license from license-file (rw)
Conditions:
Type Status
PodScheduled False
Volumes:
license-file:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: ingress-config
Optional: false
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 2m12s (x5 over 8m11s) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Name: ui-69f55568d6-knr7c
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:44:56 +0530
Labels: app=ui
date=1710760402
pod-template-hash=69f55568d6
Annotations:
Status: Running
IP: 10.1.0.184
IPs:
IP: 10.1.0.184
Controlled By: ReplicaSet/ui-69f55568d6
Containers:
ui:
Container ID: docker://d9a974bfc36343ef072d06a9ef2799bf671b8548fa2c24af20a2fd561cc06372
Image: sagcr.azurecr.io/controlplane-ui:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-ui@sha256:51f97c9f1a7414c7937e26b5fef9fba4e18890b14955a38d8958303d88a0f955
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:45:02 +0530
Ready: False
Restart Count: 0
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/controlplane/api/ui/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/controlplane/api/ui/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ui-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 7m41s (x3 over 9m1s) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Normal Scheduled 7m37s default-scheduler Successfully assigned control-plane/ui-69f55568d6-knr7c to docker-desktop
Normal Pulling 7m34s kubelet Pulling image "sagcr.azurecr.io/controlplane-ui:11.0"
Normal Pulled 7m32s kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ui:11.0" in 2.406s (2.409s including waiting)
Normal Created 7m32s kubelet Created container ui
Normal Started 7m31s kubelet Started container ui
Warning Unhealthy 6m17s kubelet Liveness probe failed: Get "http://10.1.0.184:8080/controlplane/api/ui/health/liveness": dial tcp 10.1.0.184:8080: connect: connection refused
Warning Unhealthy 6m5s (x2 over 6m17s) kubelet Readiness probe failed: Get "http://10.1.0.184:8080/controlplane/api/ui/health/readiness": dial tcp 10.1.0.184:8080: connect: connection refused
Warning Unhealthy 5m52s kubelet Readiness probe failed: Get "http://10.1.0.184:8080/controlplane/api/ui/health/readiness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 72s (x18 over 5m35s) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Name: ui-85488bd7cf-lqp74
Namespace: control-plane
Priority: 0
Service Account: default
Node:
Labels: app=ui
date=1710760456
pod-template-hash=85488bd7cf
Annotations:
Status: Pending
IP:
IPs:
Controlled By: ReplicaSet/ui-85488bd7cf
Containers:
ui:
Image: sagcr.azurecr.io/controlplane-ui:11.0
Port: 8080/TCP
Host Port: 0/TCP
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/controlplane/api/ui/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/controlplane/api/ui/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ui-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
PodScheduled False
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Warning FailedScheduling 2m12s (x5 over 8m11s) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
Name: ui-9c8c95c4f-dslgc
Namespace: control-plane
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.3
Start Time: Mon, 18 Mar 2024 16:31:05 +0530
Labels: app=ui
date=1710759663
pod-template-hash=9c8c95c4f
Annotations:
Status: Running
IP: 10.1.0.171
IPs:
IP: 10.1.0.171
Controlled By: ReplicaSet/ui-9c8c95c4f
Containers:
ui:
Container ID: docker://167fbf928b95ad446b36bf66f13e1a2332816c0bb8d22015ac274a214ea2fc58
Image: sagcr.azurecr.io/controlplane-ui:11.0
Image ID: docker-pullable://sagcr.azurecr.io/controlplane-ui@sha256:51f97c9f1a7414c7937e26b5fef9fba4e18890b14955a38d8958303d88a0f955
Port: 8080/TCP
Host Port: 0/TCP
State: Running
Started: Mon, 18 Mar 2024 16:36:03 +0530
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Mon, 18 Mar 2024 16:33:39 +0530
Finished: Mon, 18 Mar 2024 16:35:56 +0530
Ready: False
Restart Count: 2
Limits:
cpu: 500m
memory: 512Mi
Requests:
cpu: 500m
memory: 512Mi
Liveness: http-get http://:8080/controlplane/api/ui/health/liveness delay=60s timeout=5s period=20s #success=1 #failure=3
Readiness: http-get http://:8080/controlplane/api/ui/health/readiness delay=60s timeout=5s period=20s #success=1 #failure=3
Environment Variables from:
ui-config ConfigMap Optional: false
Environment:
Mounts:
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
QoS Class: Guaranteed
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 21m default-scheduler Successfully assigned control-plane/ui-9c8c95c4f-dslgc to docker-desktop
Normal Pulled 21m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ui:11.0" in 1.913s (13.845s including waiting)
Normal Killing 19m kubelet Container ui failed liveness probe, will be restarted
Warning Unhealthy 19m kubelet Readiness probe failed: Get "http://10.1.0.171:8080/controlplane/api/ui/health/readiness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Normal Pulling 18m (x2 over 21m) kubelet Pulling image "sagcr.azurecr.io/controlplane-ui:11.0"
Normal Pulled 18m kubelet Successfully pulled image "sagcr.azurecr.io/controlplane-ui:11.0" in 2.243s (2.244s including waiting)
Normal Created 18m (x2 over 21m) kubelet Created container ui
Normal Started 18m (x2 over 21m) kubelet Started container ui
Warning Unhealthy 17m (x9 over 20m) kubelet Readiness probe failed: Get "http://10.1.0.171:8080/controlplane/api/ui/health/readiness": dial tcp 10.1.0.171:8080: connect: connection refused
Warning Unhealthy 15m (x7 over 20m) kubelet Liveness probe failed: Get "http://10.1.0.171:8080/controlplane/api/ui/health/liveness": dial tcp 10.1.0.171:8080: connect: connection refused
Warning Unhealthy 83s (x50 over 14m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Is it possible to automatically create and configure Data Planes while registering API Gateway instances using the Control Plane agent?
That would be very helpful!
Setup details:
In my laptop, using docker, API Control plane started successfully with steps listed here
Running API Gateway docker container using docker compose with environment variables and steps listed here
Issue Details:
But unable to register API Gateway container as runtime with local API Control plane. I am seeing below error in Control plane startup.
jvm 1 | ISSERVER|| 2023-12-04 01:01:11 GMT [YAI.0005.9999E] (tid=579) Control plane Agent startup failed with exception:: I/O error on POST request for "https://localhost:8080/api/assetcatalog/v1/runtimes": Connection refused (Connection refused); nested exception is java.net.ConnectException: Connection refused (Connection refused)
jvm 1 | org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:791)
jvm 1 | org.springframework.web.client.RestTemplate.execute(RestTemplate.java:717)
jvm 1 | org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:608)
jvm 1 | com.softwareag.controlplane.agent.core.utils.ProxyService.callback(ProxyService.java:80)
jvm 1 | com.softwareag.controlplane.agent.core.utils.ProxyService.forwardRequest(ProxyService.java:70)
jvm 1 | com.softwareag.controlplane.agent.core.configuration.ControlPlaneProxyImpl.send(ControlPlaneProxyImpl.java:102)
jvm 1 | com.softwareag.controlplane.agent.core.configuration.ControlPlaneProxyImpl.doPost(ControlPlaneProxyImpl.java:57)
jvm 1 | com.softwareag.controlplane.agent.core.processors.RuntimeRegistrationProcessor.publishRuntimeToControlPlane(RuntimeRegistrationProcessor.java:70)
jvm 1 | com.softwareag.controlplane.agent.core.init.Agent.start(Agent.java:36)
jvm 1 | com.softwareag.controlplane.agent.apigateway.impl.RuntimeAPIGatewayDataProvider.initializeAgent(RuntimeAPIGatewayDataProvider.java:29)
jvm 1 | com.softwareag.apigateway.is.init.ISPackageManager$PostStartupRunner.run(ISPackageManager.java:566)
jvm 1 | java.base/java.lang.Thread.run(Thread.java:829)
jvm 1 | {1}
jvm 1 | ISSERVER|| 2023-12-04 01:01:11 GMT [YAI.0005.0076E] (tid=579) [default][0cec232983af] An error occurred in postStartupProcessing. Cause: I/O error on POST request for "https://localhost:8080/api/assetcatalog/v1/runtimes": Connection refused (Connection refused); nested exception is java.net.ConnectException: Connection refused (Connection refused) org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://localhost:8080/api/assetcatalog/v1/runtimes": Connection refused (Connection refused); nested exception is java.net.ConnectException: Connection refused (Connection refused)
jvm 1 | at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:791) ~[spring-web.jar:?]
jvm 1 | at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:717) ~[spring-web.jar:?]
jvm 1 | at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:608) ~[spring-web.jar:?]
jvm 1 | at com.softwareag.controlplane.agent.core.utils.ProxyService.callback(ProxyService.java:80) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.core.utils.ProxyService.forwardRequest(ProxyService.java:70) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.core.configuration.ControlPlaneProxyImpl.send(ControlPlaneProxyImpl.java:102) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.core.configuration.ControlPlaneProxyImpl.doPost(ControlPlaneProxyImpl.java:57) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.core.processors.RuntimeRegistrationProcessor.publishRuntimeToControlPlane(RuntimeRegistrationProcessor.java:70) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.core.init.Agent.start(Agent.java:36) ~[?:?]
jvm 1 | at com.softwareag.controlplane.agent.apigateway.impl.RuntimeAPIGatewayDataProvider.initializeAgent(RuntimeAPIGatewayDataProvider.java:29) ~[?:?]
jvm 1 | at com.softwareag.apigateway.is.init.ISPackageManager$PostStartupRunner.run(ISPackageManager.java:566) [?:?]jvm 1 | at java.lang.Thread.run(Thread.java:829) [?:?]
jvm 1 | Caused by: java.net.ConnectException: Connection refused (Connection refused)
jvm 1 | at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:?]
jvm 1 | at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412) ~[?:?]
jvm 1 | at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255) ~[?:?]
jvm 1 | at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237) ~[?:?]
jvm 1 | at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:?]
jvm 1 | at java.net.Socket.connect(Socket.java:615) ~[?:?]
jvm 1 | at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:305) ~[?:?]
jvm 1 | at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) ~[?:?]
jvm 1 | at sun.net.NetworkClient.doConnect(NetworkClient.java:182) ~[?:?]
jvm 1 | at sun.net.www.http.HttpClient.openServer(HttpClient.java:509) ~[?:?]
jvm 1 | at sun.net.www.http.HttpClient.openServer(HttpClient.java:604) ~[?:?]
jvm 1 | at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:266) ~[?:?]
jvm 1 | at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:373) ~[?:?]
jvm 1 | at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:207) ~[?:?]
jvm 1 | at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1192) ~[?:?]
jvm 1 | at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1086) ~[?:?]
jvm 1 | at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:193) ~[?:?]
jvm 1 | at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:168) ~[?:?]
jvm 1 | at org.springframework.http.client.SimpleBufferingClientHttpRequest.executeInternal(SimpleBufferingClientHttpRequest.java:76) ~[spring-web.jar:?]
jvm 1 | at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) ~[spring-web.jar:?]
jvm 1 | at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:66) ~[spring-web.jar:?]
jvm 1 | at org.springframework.http.client.BufferingClientHttpRequestWrapper.executeInternal(BufferingClientHttpRequestWrapper.java:63) ~[spring-web.jar:?]
jvm 1 | at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) ~[spring-web.jar:?]
jvm 1 | at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:66) ~[spring-web.jar:?]
jvm 1 | at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:782) ~[spring-web.jar:?]
jvm 1 | ... 11 more
It would be very helpful if the user could save a set of filter criteria in their profile, or, at least, if the Control Plane could save it in the session. Currently, I am losing context every time I switch from one view to another. Thanks!
Best regards,
Thomas
When I hover over an icon in the map, the cursor changes to become a link symbol (hand), but when I click the mouse button, nothing happens.
The text includes the following sentence: "API Control Plane is a single solution for understanding, managing and controlling the entire API Management landscape, regardless of where it is, on premises."
Probably you wanted to say: ... regardless of where it is, on premises or in the cloud.
The headings of the status pop-up read: Name | Health | Current | Previous.
It should be: Name | Current | Time in current health | Previous - as in the corresponding dashboard pane.
Sometimes, the data plane status does not correspond with the statuses of the included runtimes:
It is more important for the user to see the most current changes first.
The dashboard should also offer the option to filter the displayed objects. Otherwise, the map and the statistics panes are difficult to read and understand.
The Activities view for APIs shows actions like Updated, Added, Versioned etc. This information is not very helpful without knowing on which runtime the action occurred.
On the Manage APIs page, you can only filter by API tags or by runtime names:
In addition to that, I would also like to filter by runtime tags. I only want to see the APIs on my runtimes which are all marked by one specific tag, but the APIs are not marked by a specific tag.
Thanks!
Best regards,
Thomas
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.