Create A Default Client In Spring Autoconfiguration

[ryanjbaxter]

Currently if an ApiClient cannot be created when Spring AutoConfiguration is run the application will fail to start. This is common when running an app with client-java-spring-integration on the classpath but maybe starting the app outside of Kubernetes. In Spring Cloud Kubernetes we have done something like this.
https://github.com/spring-cloud/spring-cloud-kubernetes/blob/main/spring-cloud-kubernetes-client-autoconfig/src/main/java/org/springframework/cloud/kubernetes/client/KubernetesClientUtils.java#L34

I wonder if we could maybe do the same thing in the auto configuration classes in the Kuberentes Java Client?

[brendandburns]

That seems fine to me, though @yue9944882 and @dsyer have stronger opinions about Spring integration than I do.

[ryanjbaxter]

@yue9944882 let me know what you think, thanks!

[yue9944882]

SGTM! will send a pull to add the default client

[yue9944882]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ryanjbaxter]

This was fixed by #1963