[Kubernetes] graviteeio-apim3x-api not start because dial tcp 172.18.0.3:8083 connection refused

[ThomAille]

Expected Behavior

After the repo install command I should have api management deployed and operational.

Current Behavior

Possible Solution

Maybe a bad configuration in the repository or in my kubernetes

Steps to Reproduce (for bugs)

1. Launch helm repo add graviteeio https://helm.gravitee.io
2. Launch helm install graviteeio-apim3x graviteeio/apim3

Context

I am looking to install the access management and api management suite using kubernetes

Your Environment

Minikube :

minikube version: v1.12.1
commit: 5664228288552de9f3a446ea4f51c6f29bbdd0e0

Helm : version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"dirty", GoVersion:"go1.14.3"}

Kubectl :

Client Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.6-beta.0", GitCommit:"e7f962ba86f4ce7033828210ca3556393c377bcc", GitTreeState:"clean", BuildDate:"2020-01-15T08:26:26Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-20T12:43:34Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Docker : Docker version 19.03.12, build 48a66213fe

[brasseld]

Hi @ThomAille

Is this issue still relevant?

Regards,

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.