If you only want to make the default host preflight checks more restrictive, add your more restrictive host preflight checks to kurl.hostPreflights, and do not set excludeBuiltinHostPreflights. You only need to specify your customizations because the default host preflights run automatically.Ĭustomized host preflight checks run in addition to default host preflight checks, if the default host preflight checks are enabled. Under the hostPreflights field, add a host preflight specification ( kind: HostPreflight) with your customizations. (Optional) To run customized host preflight checks in addition to the default host preflight checks, add a hostPreflights field to the kurl field in your Installer manifest. In this case, no host preflight checks are run.ĮxcludeBuiltinHostPreflights is an aggregate flag, so setting it to true disables the default host preflights for Kubernetes and all included add-ons. (Optional) To disable the default host preflight checks for Kubernetes and all included add-ons, add the kurl field to your Installer manifest and add kurl.excludeBuiltinHostPreflights: true to your Installer manifest. For more information, see Creating a Kubernetes Installer. This procedure gives examples of the customization options.Ĭreate a Kubernetes installer ( kind: Installer). You can also customize the outcomes to enforce warnings or ignore failures. You can customize the host preflight checks by disabling them entirely, adding customizations to the default checks to make them more restrictive, or completely customizing them. The default host preflights run automatically as part of your Kubernetes installer.
#Preflight checklists license
Exclude certain preflights under specific conditions, such as when a particular license entitlement is enabled.There are also host preflight checks included with certain add-ons. There are general kURL host preflight checks that run with all installers. For a complete list of default host preflight checks, see Default Host Preflights in the kURL documentation. Additionally, some checks only run when certain add-ons are enabled in the installer. The default host preflight checks that run can vary, depending on whether the installation is new, an upgrade, joining a node, or an air gap installation.
#Preflight checklists update
Users can then update their environment and run the Kubernetes installer again to re-run the host preflight checks. Default host preflight failures block the installation from continuing and exit with a non-zero return code.
For more information about application checks, collectors, and analyzers, see Customizing Preflight Checks and Support Bundles.ĭefault host preflight checks verify conditions such as operating system and disk usage. While host preflights are intended to ensure requirements are met for running the cluster, you can also use them to codify some of your application requirements so that users get feedback even earlier in the installation process, rather than waiting to run preflights after the cluster is already installed. This helps to ensure successful installation and the ongoing health of the cluster. You can include host preflight checks with Kubernetes installers to verify that infrastructure requirements are met for:
#Preflight checklists how to
This topic provides information about how to customize host preflight checks for Kubernetes installers. or gasoline powered models).Customizing Host Preflight Checks for Kubernetes Installers
Note to Instructor: Check new or rebuilt aircraft very carefully. (Done at the field by the instructor with the student following along)
0 kommentar(er)
