Hello, I noticed that If the service type is changed back to NodePor

Daemonset Not Deleted about akrobateo HOT 3 OPEN

kontena commented on June 24, 2024

Daemonset Not Deleted

from akrobateo.

Comments (3)

jnummelin commented on June 24, 2024

Indeed. Now the operator ignores every change on a service which is not a type: LoadBalancer.

from akrobateo.

infinitydon commented on June 24, 2024

Is this meant to fix the bug?

I just tested with the echoserver deployment example, changed the svc type to NodePort but the DS stil remains.

Name:                     echoserver
Namespace:                default
Labels:                   <none>
Annotations:              kubectl.kubernetes.io/last-applied-configuration:
                            {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"name":"echoserver","namespace":"default"},"spec":{"ports":[{"name":"echo...
Selector:                 app=echoserver
Type:                     NodePort
IP:                       10.233.45.107
Port:                     echo  8080/TCP
TargetPort:               8080/TCP
NodePort:                 echo  30078/TCP
Endpoints:                10.233.66.127:8080
Port:                     echo2  9090/TCP
TargetPort:               8080/TCP
NodePort:                 echo2  31951/TCP
Endpoints:                10.233.66.127:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
  Type    Reason  Age   From                Message
  ----    ------  ----  ----                -------
  Normal  Type    2m    service-controller  LoadBalancer -> NodePort

from akrobateo.

jnummelin commented on June 24, 2024

There's no fix yet for this. I haven't had yet time to looks at how to do this properly.

from akrobateo.

Recommend Projects