Skip to content
New issue

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

🌱 clusterctl: always run crd migration if possible to reduce conversion webhook usage #10513

Commits on Apr 25, 2024

  1. clusterctl: always run crd migration if possible to reduce conversion…

    … webhook usage
    
    If objects are still stored in the old version, every time an object is requested
    the kube-apiserver will call the conversion webhook. Instead of lots of conversion
    webhook calls we once do the migration if possible.
    
    Also increases the timeout used for the migrations: Before running CRD migration
    clusterctl usually upgrades cert-manager which may lead to updating Certificates and
    rolling out new certificates to our controllers. There is a chance that this can take
    up to 90s in which conversion, validating or mutatingwebhooks may be unavailable.
    Because the migration gets run more aggresively during upgrades this also increases
    the relevant timeouts.
    chrischdi committed Apr 25, 2024
    Configuration menu
    Copy the full SHA
    d754ad5 View commit details
    Browse the repository at this point in the history

Commits on Apr 26, 2024

  1. review fixes

    chrischdi committed Apr 26, 2024
    Configuration menu
    Copy the full SHA
    4a7acb0 View commit details
    Browse the repository at this point in the history

Commits on Apr 30, 2024

  1. review fixes

    chrischdi committed Apr 30, 2024
    Configuration menu
    Copy the full SHA
    b46a303 View commit details
    Browse the repository at this point in the history