Skip to content

Claudie v0.9.7

Choose a tag to compare

View all tags
@Despire Despire released this 12 Mar 13:18
· 150 commits to master since this release
v0.9.7
600878b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.9.7

What's Changed

  • Additional settings were added to roles for LoadBalancers. #1685.

    It is now possible to configure adding/removing proxy protocol and sticky sessions.

    stickySessions will always forward traffic to the same node based on the IP hash.

    proxyProtocol will turn on the proxy protocol. If used, the application to which the traffic is redirected must support this protocol.

      loadBalancers:
  roles:
    - name: example-role
      protocol: tcp
      port: 6443
      targetPort: 6443
      targetPools:
        - htz-kube-nodes
      # added
      settings:
        proxyProtocol: off (default will be on)
        stickySession: on. (default will be off)

  • Claudie will now ping nodes to check If any of the nodes became unreachable, Claudie will report the problem and will not work on any changes until the connectivity issue is resolved. #1658

    For unreachable nodes within the kubernetes cluster, Claudie will give you the options of resolving the issue or removing the node from the InputManifest or via kubectl, Claudie will report the following issue

    fix the unreachable nodes by either:
 - fixing the connectivity issue
 - if the connectivity issue cannot be resolved, you can:
   - delete the whole nodepool from the kubernetes cluster in the InputManifest
   - delete the selected unreachable node/s manually from the cluster via 'kubectl'
     - if its a static node you will also need to remove it from the InputManifest
     - if its a dynamic node claudie will replace it.
     NOTE: if the unreachable node is the kube-apiserver, claudie will not be able to recover
           after the deletion.

    For unreachable nodes within the loadbalancer cluster, Claudie will give you the options of resolving the issue or removing the nodepool or load balancer from the InputManifest, Claudie will report the following issue

    fix the unreachable nodes by either:
 - fixing the connectivity issue
 - if the connectivity issue cannot be resolved, you can:
   - delete the whole nodepool from the loadbalancer cluster in the InputManifest
   - delete the whole loadbalancer cluster from the InputManifest

Bug fixes

  • It may be the case that the cluster-autoscaler image may not share the same version as the specified kubernetes version in the InputManifest. Claudie will now correctly recognize this and pick the latest available cluster-autoscaler image #1680

  • Claudie will now set the limits of max open file descriptors on each node to 65535 #1679

Assets 6
Loading