Closed thesse1 closed 10 months ago
FYI: I managed to make it work using environment variables instead of cp-agent.yml ConfigMap. But it would be much more convenient (and closer to Kubernetes best practices, I believe) to inject the configuration using ConfigMap. Why is that not working?
@thesse1
The agentConfig key is missing in the YAML file. It should be as `below.
cp-agent.yml:
----
agentConfig:
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: "thomas.hesse@softwareag.com"
password: "***"
@thesse1 Did you have a chance to try out this?
@MadhavanKidambiVaradan Thanks for your help! It is working fine with the agentConfig key. Thanks!
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:
But the API Gateway does not show up in the Control Plane. In server.log, I found the following NullPointerException:
PFA the full server.log file.
I also tried with just the mandatory parameters:
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:
Thanks! Best regards, Thomas