spring-cloud-commons | Common classes used in different Spring Cloud | Microservice library

As mentioned here https://github.com/spring-projects/spring-boot/issues/25049#event-4265028906

Declaring a bean of type LoadBalancerClientFactory containing the list of all applicable LoadBalancerClientSpecification did the trick. Pretty straightforward but had to dig around to figure out which bean to expose as there was no example that I could find.

This might have to do with you not using Generics with your java Collections

As of Spring Boot 2.4, JUnit 5’s vintage engine has been removed from spring-boot-starter-test. If we still want to write tests using JUnit 4, we need to add the following Maven dependency:

Change your application.yml as follow :

Well the correct term is that @EnableAuthorizationServer is in maintenance mode which basically means deprecated. As in there will be no added features or updates.

The story goes basically as follows.

During Spring 4 i believe there was a single person that maintained the oauth2 part of spring security. When Spring security 5 was launched the team at pivotal decided to do a major overhaul of spring security and the oauth2 parts. So what they did was to drop Authorisation server support, and instead focus on the Resource server support at first.

Spring announcement of dropping Authorisation server support

You have pulled in spring-cloud-starter-oauth2 which in turn har a peer dependency on spring-security-oauth2-autoconfigure which in turn pulls in spring-security-oauth2.

Here Spring clearly states that if you wish to use spring-security-oauth2 they will help you out, but it is in maintenance mode.

The choice to not support it was made because an authorization server is like owning a product. Spring doesn't maintain their own database, or own Ldap server etc. There are plenty of auth servers out there that can be used, okta, curity, github, fb, google, etc, etc.

But Spring has actually reevaluated that choice and decided to start a community developed open source authorisation server

So you have 3 choices:

• use the old, that is in maintenance mode
• use a 3rd party vendor, github, fb, google, okta, curity etc.
• try out the new open source authorisation server

As pointed put by Nicoll, With Spring Cloud Vault 3.0 and Spring Boot 2.4, the bootstrap context initialization (bootstrap.yml, bootstrap.properties) of property sources was deprecated. This can be fixed in one of the 2 ways

1. Use Spring Boot 2.4.0 Config Data API to import configuration from Vault
2. Enable the bootstrap context either by setting the configuration property spring.cloud.bootstrap.enabled=true or by including the dependency org.springframework.cloud:spring-cloud-starter-bootstrap

1. Use Spring Boot 2.4.0 Config Data API

Move bootstrap.yml configuration to application.yml and define spring.config.import to import all profiles. And it looks like below

The el filter must return a boolean value. The discovered service, which should be filtered, is injected as #root in the expression. So #root.metadata.name retrieves the actual name of the kubernetes service.

This part of code of KubernetesDiscoveryClient does the filtering:

Seems you're likely using an account that isn't authorised from what I can find online. There's little in the way of a single solution I can identify one, but there is one potentially helpful resource:

https://stackoverflow.com/a/58701728/7619034

There were others but SO doesn't like links (to external sites). I can suggest if this does not help at all