spring-cloud-kubernetes: Spring Cloud Kubernetes cant refresh config

May be caused by kubersphere enterprise space permissions，The default token does not have enterprise space authorization, so when I start it, I will prompt 401unauthorized and 403 forbidden，I modified the enterprise space permissions, and then it worked.

I still can’t reproduce it. I’ve create a PR for your project, see here

Here is what I do:

• 1. create a local cluster (I am using kind), this is needed to be able to curl on the NodePort

kind create cluster --config k8s/kind.yaml

• 1. kubectl proxy --port=8092 and in a different terminal: curl http://localhost:8092/api. This will show something like this:

{
  "kind": "APIVersions",
  "versions": [
    "v1"
  ],
  "serverAddressByClientCIDRs": [
    {
      "clientCIDR": "0.0.0.0/0",
      "serverAddress": "172.18.0.3:6443"
    }
  ]
}

all I need is the serverAddress. In my case: 172.18.0.3:6443. Take this value and place it in application.yaml:

      client:
        master-url: "https://172.18.0.3:6443"

• 1. build the docker image (I am not using the Dockerfile), but instead (notice in my PR that I have changed the pom.xml):

mvn clean install -Dspring-boot.build-image.builder=dashaun/builder:tiny 

I only need -Dspring-boot.build-image.builder=dashaun/builder:tiny because I am on ARM Cpu, if you are not, you might not need that.

• 1. check that the image has been created:

wind57@wind57s-MacBook-Pro /p/t/istio-master (try-to-reproduce-on-my-own-branch)> docker images | grep master
springcloud/master                                                            0.0.1-SNAPSHOT   0a9d4e410416   43 years ago    228MB

Please note that I have also changed:

      containers:
        - name: master
          image: docker.io/springcloud/master:0.0.1-SNAPSHOT
          imagePullPolicy: IfNotPresent

• 1. load the image into kind:

kind load docker-image springcloud/master:0.0.1-SNAPSHOT

• 1. create the namespace:

kubectl create ns istio-example

• 1. apply manifests

kubectl apply -f k8s/privileges.yaml
kubectl apply -f k8s/config-map.yaml
kubectl apply -f k8s/deployment.yaml
kubectl apply -f k8s/service.yaml

• 1. see the current value:

wind57@wind57s-MacBook-Pro /p/t/istio-master (try-to-reproduce-on-my-own-branch) [56]> curl  localhost:30950/api/devValue
application-dev-profile11

• 1. Edit config-map:

kubectl edit configmap master -n istio-example

• 1. curl again:

wind57@wind57s-MacBook-Pro /p/t/istio-master (try-to-reproduce-on-my-own-branch)> curl  localhost:30950/api/devValue
application-dev-profile12

---

If you can tell me how I ca re-produce this one against my PR that I made, that would be lovely. Thank you

I had to go through quite a few hoops to get this running: you have not defined RBAC for the service account, not said how you build the docker image, your app the way it is would fail start-up with some dependency miss-configuration… Next time, pretty please, make sure you provide a complete and minimal example, otherwise I might miss what set-up you have exactly.

What I had to do with your app (besides creating the RBAC rules for the service account) is to remove bootstrap.yaml and the spring-cloud-starter-bootstrap dependency. Otherwise, you have both config-data and bootstrap, so there would be a certain bean created two times and Spring context would not start.

After I removed the above mentioned, created the image (using the spring-boot plugin), I deployed the config-map and deployment and then did :

kubectl get pods -o wide

to find out the IP of the pod (since you have not provided a service and ingress either). Then:

curl 10.244.0.15:8080/api/devValue

and got the application-dev-profile11 as a response. So far, you get the same result.

Then, I did a kubectl edit configmap master (notice that I have simplified your initial example by not including the namespace you had, its only to make my life easier 😃 )

and then did another curl, and I got the new value as a response, the updated one.

Notice that I did not have to do any POST localhost:8080/actuator/refresh, because you already have:

....
      reload:
        monitoring-config-maps: true
        enabled: true
        strategy: refresh

and the refresh will happen automatically.

---

Unless you have an example where your problem is really re-producible, there is nothing I can do more.

@ryanjbaxter can you please add the proper label in here? We need to get proper feedback from OP, otherwise it should be closed. thank you

oh sorry, idea setting repository is private ,im changed. you can access