We committed my alterations in a part and you can pressed to help you Bitbucket

I’ll know, I’m a big enthusiast out-of function twigs and you may happy with they. I understand several of my colleagues will likely offer myself heck regarding (thinking about you Thomas Traude ). A few minutes after We acquired an alerts that my personal Jenkins create try yellow.

۱ [ERROR] coffee.lang.IllegalStateException: Did not weight ApplicationContext 2 Because of: org.springframework.kidney beans.facility.UnsatisfiedDependencyException: Mistake starting bean that have identity 'kubernetesKubectlCreateProcessor' : Disappointed dependency conveyed owing to job 'apiClient' ; nested difference is org.springframework.beans.factory.BeanCreationException: Mistake carrying out bean that have name 'defaultApiClient' outlined in group highway funding step three cuatro Caused by: org . springframework . beans . factory . BeanCreationException: Error creating bean with name ' defaultApiClient ' defined in class path resource 5 6 Caused by: org . springframework . beans . BeanInstantiationException: Filipino chicas calientes Failed to instantiate [ io . kubernetes . consumer . openapi . ApiClient ]: Warehouse means ' defaultApiClient ' tossed exception ; nested exception is java . io . FileNotFoundException: . ( Was a index ) eight Caused by: java . io . FileNotFoundException: . ( Is a directory ) 

Looks like we have some flaky tests. Depending on the environment, the application context may fail to load. This is the very definition of frustrating, but don't worry, I enjoy these kinds of challenges.

In case you're asking yourself why the tests fail if the builds run in Kubernetes, that's because they don't. Our Jenkins jobs don't run in Kubernetes, since we make extensive use of Testcontainers . If you don't use them, be sure to check them out, awesome. And their new cloud solution looks very promising.

Disabling Springtime Affect Kubernetes into the tests

Spring Cloud Kubernetes can be disabled in tests using the property .kubernetes.enabled . Drop that property into your tests like so, and you're good to go (or at least it used to work).

۱( "test" ) 2(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_Port, 3 properties ="spring.cloud.kubernetes.enabled=false" >) 4 class ApplicationIT < 5 > 

I didn't understand the issue at first, it should have been disabled. We've been using the new Kubernetes Java Client successfully in other projects, and there the tests aren't flaky. I took another look, turns out that our projects are using different versions. Version 2020.0.1 works as expected.

A change introducing additional configuration properties in the Kubernetes Java Client had an unintentional side-effect; the property .kubernetes.enabled no longer works as expected. There is no longer a single property to disable Spring Cloud Kubernetes.

Issues have been reported here and here , with the fixes scheduled for 2020.0.5 . Unfortunately, as of writing this article, version 2020.0.5 hasn't been released. This enhancement was included in Spring Cloud 2020.0.2 , which explains why the version 2020.0.1 worked in other projects.

Second attempt – utilizing the existing fabric8 consumer

۱  dependency > 2  groupId > org.springframework.affectgroupId > 3  artifactId > spring-cloud-starter-kubernetes-fabric8-configartifactId > 4dependency > 

Locally the build is green. Push to Jenkins, and wait. Crossing my fingers always helps, so that's what I did. And what do you know, worked like a charm; no issues, nothing, zero, zip. I love when things just work.

I should have known better. The fabric8 client has been serving us well for many years. Don't mess with a running system!

Instructions discovered upgrading Spring season Cloud Kubernetes

It would appear the Spring Cloud Kubernetes Java Client is not yet ready. The Kubernetes Java Client introduced their own Spring integration which doesn't integrate with the Spring configuration properly. Hopefully the two projects are cooperating, and we'll get a nice clean Spring-based configuration in the future. Once version 2020.0.5 is released, I'll give it another try.