Spring-Boot-Demo | Spring Boot 实战 | Application Framework library

It doesn't work because of the known IntelliJ IDEA bug specific to Spring Boot 2.2.x versions.

I think you should think about using Headless services.

Sometimes you don’t need or want load-balancing and a single service IP. In this case, you can create what are termed “headless” Services, by explicitly specifying "None" for the cluster IP (.spec.clusterIP).

You can use a headless Service to interface with other service discovery mechanisms, without being tied to Kubernetes’ implementation. For example, you could implement a custom [Operator]( be built upon this API.

For such Services, a cluster IP is not allocated, kube-proxy does not handle these services, and there is no load balancing or proxying done by the platform for them. How DNS is automatically configured depends on whether the service has selectors defined.

For your example if you set service to spec.clusterIP = None you could nslookup -type=A spring-boot-demo-pricing which will show you IPs of pods attached to this service.

1. No you need not to run kubeadm init or kubectl apply -f "https://cloud.weave...... in worker nodes. Check

2. To use kubectl commands from worker nodes you need to transfer the /etc/kubernetes/admin.conf file to worker nodes and put it in /{username}/.kube/config

scp /etc/kubernetes/admin.conf {workerNoderUser}@{workerNoderIP}:/{username}/.kube/config

once you transfer the config you can run kubectl commands in worker nodes as well.

1. There can be many reasons for not being able to ping from the worker node's pod. First check if your worker node itself can ping to google.com or not. if that works then check your cluster dns which is kube-dns or coredns, check their logs and if they are healthy. you may also try to delete the /etc/resolv.conf and add public dns servers like that of google's (8.8.8.8). Lastly you can follow this

The error message means you are missing a bundle that provides one of the requirements of your bundle.

You find the missing requirement at the end of this long error message:

I think the error is because the new spring boot bundles or dependencies are multi release jars that the maven bundle plugin version 3.3.0 can not yet handle. Updating the maven bundle plugin version to 4.1.0 fixed the issue for me.

See this PR.

So you want to replace every token in the given List ?

Here's how I would do it with streams :

1. Iterate over lines
2. parse each line only once
3. the parsing iterates over attributes, and replaces the current attribute

The String[] pLine may be was you were missing...

If you would annotate your commands with @Transactional (because this is where the entities got loaded) it will work. The underlying problem is that if you load an entity it will open a new transaction with a new session (context), find the relationships and cache the information about them in the context. The transaction (and session) will then get closed because the operation is done.

The subsequent save/update does not find an opened transaction and will then, as a consequence, open a new one (with new session/ session context). When executing the save it looks at the entity in the current state and does not see the old relationship anymore.

Two answers:

1. it is a bug ;(

EDIT: After a few days thinking about this, I revert the statement above. It is not a real bug but more like unexpected behaviour. There is nothing wrong in SDN. It uses two sessions (one for each operation) to do the work and since nobody told it to do the work in one transaction the loaded object is not 'managed' or 'attached' (as in JPA) to a session context.

1. you can work around this by using an explicit transaction for your unit of work

I will close the issue for SDN and try to migrate all the information to one of the two issues on GitHub because it is a OGM problem.

My problem was solved using these dependencies

First change your pom file like this :