microbean / helm-maven-plugin

A Maven plugin for Helm, the Kubernetes package manager.
https://microbean.github.io/helm-maven-plugin
Apache License 2.0
9 stars 3 forks source link

UNAVAILABLE: Network closed for unknown reason #49

Open fbalicchia opened 6 years ago

fbalicchia commented 6 years ago

Hi,

Executing installation plugin return with the following error

[ERROR] Failed to execute goal org.microbean:helm-maven-plugin:2.8.2.1.1.2-SNAPSHOT:install (Install your-project chart) on project demomicrotest: io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason -> [Help 1]

Configuration looks like :

<plugin>
           <groupId>org.microbean</groupId>
                <artifactId>helm-maven-plugin</artifactId>
                <version>2.8.2.1.1.2-SNAPSHOT</version>
                <executions>
                    <execution>
                        <id>Install your-project chart</id>
                        <phase>install</phase>
                        <goals>
                            <goal>install</goal>
                        </goals>
                        <configuration>
                            <chartUrl>file:${project.basedir}/demomicrotest-helm</chartUrl>
                            <releaseName>${project.name}</releaseName>
                            <valuesYamlUri>file:${project.basedir}/demomicrotest-helm/values.yaml</valuesYamlUri>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

Using helm client my charts has no problem. I'm testing it on minikube.

Could you please help me to understand where I mistake in configuration ?

Thanks

ljnelson commented 6 years ago

Hello; thanks for using the helm-maven-plugin project.

Your configuration looks fine.

helm-maven-plugin uses the microBean Helm project under the covers, and that project uses the fabric8 Kubernetes client library. It is that library which governs how network connections to Tiller, Helm's back-end component, are made. Specifically, there are a lot of configuration sources that are tried by default. I suspect that this is probably the source of your problem. Good luck!

dallasvaughan commented 5 years ago

I'm getting the same issue. It's using the config file in ~/.kube and that configuration is correct (it works with using helm otherwise).

ljnelson commented 5 years ago

I'm not sure what to tell you. As you can see from the exception, it is related to the Java implementation of the gRPC protocol (i.e. it's not something I have control over). Maybe after debugging you could try filing a more specific issue in the https://github.com/grpc/grpc-java project?