Comment 8 for bug 1820928

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-config (master)

Reviewed: https://review.openstack.org/649289
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=0d61ade5b9eff7d4f9c61f43c25cdf9a7043f8c0
Submitter: Zuul
Branch: master

commit 0d61ade5b9eff7d4f9c61f43c25cdf9a7043f8c0
Author: Bart Wensley <email address hidden>
Date: Tue Apr 2 06:54:43 2019 -0500

    Fix application-apply of stx-openstack on simplex

    The application-apply of the stx-openstack application on
    simplex configurations has been failing since the barbican
    chart was added to the application. The failure was due
    to lost node status messages from the kubelet to the
    kube-apiserver, which causes the node to be marked
    NotReady and endpoints to be removed.

    The root cause is the kubernetes bug here:
    https://github.com/kubernetes/kubernetes/issues/74412

    In short, the addition of the barbican chart added enough
    new secrets/configmaps that the kubelet hit the limit of
    http2-max-streams-per-connection. As done upstream, the
    fix is to change the following kubelet config:
    configMapAndSecretChangeDetectionStrategy (from Watch to
    Cache).

    Change-Id: Ic816a91984c4fb82546e4f43b5c83061222c7d05
    Closes-bug: 1820928
    Signed-off-by: Bart Wensley <email address hidden>