We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I noticed that If the service type is changed back to NodePort, the load balancer Daemonset is not deleted.
The text was updated successfully, but these errors were encountered:
Indeed. Now the operator ignores every change on a service which is not a type: LoadBalancer.
type: LoadBalancer
Sorry, something went wrong.
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
There's no fix yet for this. I haven't had yet time to looks at how to do this properly.
No branches or pull requests
Hello,
I noticed that If the service type is changed back to NodePort, the load balancer Daemonset is not deleted.
The text was updated successfully, but these errors were encountered: