Meta tags:
description= Chef Infra Client v 19;
Headings (most frequently used words):
chef, infra, client, run, components, how, works, common, use, cases, the, related, content, next, steps, compliance, phase, node, cookbooks, and, recipes, list, ohai, agentless,
Text of the page (most frequently used words):
chef (115), the (105), infra (90), #client (82), and (49), node (49), run (37), ohai (21), resources (21), about (20), recipes (19), attributes (19), are (18), cookbooks (18), from (18), object (18), server (17), resource (17), for (16), all (16), compliance (16), that (16), list (15), attribute (15), solo (12), agentless (11), phase (11), this (11), executable (11), handlers (11), data (11), custom (11), files (11), install (10), with (10), runs (10), configuration (10), overview (10), cookbook (9), system (9), your (8), inspec (8), each (8), loaded (8), security (8), mode (8), guide (8), windows (8), checking (8), azure (8), policy (7), next (7), you (7), community (7), order (7), file (7), use (6), nodes (6), when (6), search (6), every (6), troubleshooting (6), dsl (6), plugins (6), any (5), steps (5), common (5), how (5), components (5), which (5), collection (5), information (5), then (5), first (5), language (5), ruby (5), rebuilt (5), metadata (5), configure (5), environments (5), management (5), infrastructure (5), state (5), progress (4), trademarks (4), page (4), content (4), works (4), lists (4), complete (4), during (4), libraries (4), policyfiles (4), including (4), name (4), policies (4), requirements (4), required (4), execute (4), glossary (4), policyfile (4), handler (4), reference (4), extension (4), migrating (4), migration (4), directory (4), integrations (4), reading (4), bags (4), installation (4), microsoft (4), cloud (4), air (4), gapped (4), online (4), upgrade (4), software (3), its (3), other (3), see (3), their (3), licensing (3), related (3), cases (3), table (3), contents (3), can (3), workstation (3), audit (3), report (3), within (3), get (3), identified (3), process (3), based (3), execution (3), according (3), precedence (3), templates (3), downloads (3), using (3), key (3), gets (3), automatically (3), desired (3), tool (3), types (3), herein (2), corporation (2), one (2), subsidiaries (2), affiliates (2), appropriate (2), rights (2), reserved (2), respective (2), owners (2), not (2), 2026 (2), modified (2), feedback (2), contact (2), time (2), tests (2), checks (2), reporting (2), defined (2), legacy (2), current (2), profile (2), processes (2), appropriately (2), finishes (2), profiles (2), always (2), exception (2), present (2), actions (2), have (2), been (2), will (2), pull (2), down (2), available (2), configures (2), listed (2), defines (2), action (2), part (2), called (2), also (2), compile (2), reset (2), dependencies (2), updated (2), default (2), previous (2), new (2), contains (2), rsa (2), private (2), following (2), across (2), continuously (2), different (2), automate (2), details (2), instructions (2), documentation (2), allows (2), without (2), detailed (2), systems (2), into (2), deprecations (2), supermarket (2), ctl (2), apis (2), lwrps (2), notes (2), unified (2), rest (2), definitions (2), partials (2), helpers (2), accumulators (2), zypper_repository (2), zypper_package (2), yum_repository (2), yum_package (2), windows_workgroup (2), windows_user_privilege (2), windows_update_settings (2), windows_uac (2), windows_task (2), windows_shortcut (2), windows_share (2), windows_service (2), windows_security_policy (2), windows_printer_port (2), windows_printer (2), windows_path (2), windows_pagefile (2), windows_package (2), windows_font (2), windows_firewall_rule (2), windows_firewall_profile (2), windows_feature_powershell (2), windows_feature_dism (2), windows_feature (2), windows_env (2), windows_dns_zone (2), windows_dns_record (2), windows_dfs_server (2), windows_dfs_namespace (2), windows_dfs_folder (2), windows_defender_exclusion (2), windows_defender (2), windows_certificate (2), windows_auto_run (2), windows_audit_policy (2), windows_ad_join (2), user_ulimit (2), user (2), timezone (2), template (2), systemd_unit (2), sysctl (2), swap_file (2), sudo (2), subversion (2), ssh_known_hosts_entry (2), solaris_package (2), snap_package (2), smartos_package (2), service (2), selinux_user (2), selinux_state (2), selinux_port (2), selinux_permissive (2), selinux_module (2), selinux_login (2), selinux_install (2), selinux_fcontext (2), selinux_boolean (2), script (2), ruby_block (2), rpm_package (2), route (2), rhsm_subscription (2), rhsm_repo (2), rhsm_register (2), rhsm_errata_level (2), rhsm_errata (2), remote_file (2), remote_directory (2), registry_key (2), reboot (2), python (2), powershell_script (2), powershell_package_source (2), powershell_package (2), portage_package (2), plist (2), perl (2), paludis_package (2), pacman_package (2), package (2), osx_profile (2), openssl_x509_request (2), openssl_x509_crl (2), openssl_x509_certificate (2), openssl_rsa_public_key (2), openssl_rsa_private_key (2), openssl_ec_public_key (2), openssl_ec_private_key (2), openssl_dhparam (2), openbsd_package (2), ohai_hint (2), notify_group (2), msu_package (2), mount (2), mdadm (2), macports_package (2), macosx_service (2), macos_userdefaults (2), macos_pkg (2), log (2), locale (2), link (2), launchd (2), ksh (2), kernel_module (2), ips_package (2), inspec_waiver_file_entry (2), inspec_waiver (2), inspec_input (2), ifconfig (2), http_request (2), hostname (2), homebrew_update (2), homebrew_tap (2), homebrew_package (2), homebrew_cask (2), habitat_user_toml (2), habitat_sup (2), habitat_service (2), habitat_package (2), habitat_install (2), habitat_config (2), group (2), git (2), gem_package (2), freebsd_package (2), dsc_script (2), dsc_resource (2), dpkg_package (2), dnf_package (2), dmg_package (2), csh (2), cron_d (2), cron_access (2), cron (2), cookbook_file (2), chocolatey_source (2), chocolatey_package (2), chocolatey_installer (2), chocolatey_feature (2), chocolatey_config (2), chef_vault_secret (2), chef_user (2), chef_sleep (2), chef_role (2), chef_organization (2), chef_node (2), chef_handler (2), chef_group (2), chef_gem (2), chef_environment (2), chef_data_bag_item (2), chef_data_bag (2), chef_container (2), chef_client_trusted_certificate (2), chef_client_systemd_timer (2), chef_client_scheduled_task (2), chef_client_launchd (2), chef_client_hab_ca_cert (2), chef_client_cron (2), chef_client_config (2), chef_client (2), chef_acl (2), cab_package (2), build_essential (2), breakpoint (2), bff_package (2), batch (2), bash (2), archive_file (2), apt_update (2), apt_repository (2), apt_preference (2), apt_package (2), alternatives (2), single (2), bundled (2), functionality (2), shelling (2), out (2), secrets (2), registry (2), keys (2), tags (2), logging (2), editing (2), platforms (2), hypervisors (2), clouds (2), architectures (2), versioning (2), debug (2), json (2), yaml (2), sources (2), persistence (2), arrays (2), repo (2), fips (2), roles (2), powershell (2), shell (2), vmware (2), google (2), platform (2), supported (2), example (2), features (2), apply (2), license (2), working (2), proxies (2), bootstrap (2), cli (2), installer (2), quickstart (2), version (2), training (2), blog (2), main (2), certain, product, names, used, registered, countries, markings, contained, inclusion, does, imply, endorsement, affiliation, sponsorship, between, copyright, last, may, cookie, privacy, trademark, terms, site, map, thank, submit, fill, field, improve, document, ask, support, still, stuck, yes, was, helpful, everything, configured, stops, waits, until, asked, stop, wait, finish, running, them, send, save, after, begins, retrieves, either, presence, processed, completed, successfully, updates, built, makes, update, has, collected, executed, recipe, specific, convergence, converge, identifies, builds, ensure, extensions, classes, followed, finally, specified, expanded, additional, lexical, sort, found, these, well, requests, providers, needs, responds, compares, already, exist, copy, synchronize, expands, compiles, exact, they, applied, expand, pulls, rebuilds, discovered, set, creates, hasn, yet, had, won, entry, subsequent, rebuild, api, authentication, requires, validator, generates, authenticates, authenticate, important, piece, provides, typically, fqdn, unique, organization, node_name, happens, describes, takes, command, diagram, shows, various, stages, occur, maintain, consistent, configurations, development, staging, production, environment, check, correct, changes, drift, prevention, enforce, deploy, applications, application, deployment, servers, settings, provisioning, tasks, operates, model, where, periodically, retrieve, approach, ensures, remains, even, individual, experience, temporary, disconnections, issues, more, setup, target, over, ssh, having, installed, profiling, collects, hardware, network, operating, uses, make, intelligent, decisions, should, what, customize, contain, tell, describe, like, packages, services, represents, manages, whether, virtual, machine, container, instance, physical, maintains, define, integrated, feature, regulatory, managing, separate, tools, manage, summary, taking, compiling, loading, synchronizing, registering, authenticating, performs, bring, expected, agent, locally, under, transforms, code, configuring, match, menu, skip,
Text of the page (random words):
selinux_permissive selinux_port selinux_state selinux_user service smartos_package snap_package solaris_package ssh_known_hosts_entry subversion sudo swap_file sysctl systemd_unit template timezone user user_ulimit windows_ad_join windows_audit_policy windows_auto_run windows_certificate windows_defender windows_defender_exclusion windows_dfs_folder windows_dfs_namespace windows_dfs_server windows_dns_record windows_dns_zone windows_env windows_feature windows_feature_dism windows_feature_powershell windows_firewall_profile windows_firewall_rule windows_font windows_package windows_pagefile windows_path windows_printer windows_printer_port windows_security_policy windows_service windows_share windows_shortcut windows_task windows_uac windows_update_settings windows_user_privilege windows_workgroup yum_package yum_repository zypper_package zypper_repository custom resources custom resource guide accumulators helpers partials migrating from definitions rest resource unified mode migration notes migrating from lwrps glossary extension apis handlers custom handlers handler dsl community handlers compliance dsl ohai plugins custom plugins community plugins reference chef client executable chef solo executable handler dsl ohai executable supermarket ctl client rb metadata rb policyfile rb solo rb chef infra client deprecations glossary troubleshooting version chef infra client 19 chef infra client 19 chef infra client 18 chef infra client overview chef infra overview nodes quickstart install overview system requirements installer install troubleshooting migration tool overview online install air gapped upgrade online upgrade cli reference install using bootstrap air gapped installation client rb working with proxies licensing apply a license troubleshooting features compliance phase handlers search agentless mode about agentless mode agentless mode example resources custom resource guide supported resources chef solo about chef solo chef solo executable solo rb ohai about ohai ohai executable integrations google cloud platform vmware azure chef workstation in azure cloud shell microsoft azure powershell microsoft azure chef extension windows chef for windows windows installation guide policy about policy about policyfiles policyfile rb data bags run lists environments roles security chef infra client security fips cookbooks about cookbooks about chef repo cookbook directory attributes attributes attributes arrays attribute persistence attribute precedence attribute sources attribute types files libraries metadata rb recipes about recipes json yaml recipes debug recipes client runs templates versioning cookbooks infra language language overview checking architectures checking clouds checking hypervisors checking platforms cookbook execution editing resources logging node tags reading data bags reading registry keys search secrets management integrations shelling out windows ruby guide resources about resources common resource functionality bundled resources all resources single page alternatives apt_package apt_preference apt_repository apt_update archive_file bash batch bff_package breakpoint build_essential cab_package chef_acl chef_client chef_client_config chef_client_cron chef_client_hab_ca_cert chef_client_launchd chef_client_scheduled_task chef_client_systemd_timer chef_client_trusted_certificate chef_container chef_data_bag chef_data_bag_item chef_environment chef_gem chef_group chef_handler chef_node chef_organization chef_role chef_sleep chef_user chef_vault_secret chocolatey_config chocolatey_feature chocolatey_installer chocolatey_package chocolatey_source cookbook_file cron cron_access cron_d csh directory dmg_package dnf_package dpkg_package dsc_resource dsc_script execute file freebsd_package gem_package git group habitat_config habitat_install habitat_package habitat_service habitat_sup habitat_user_toml homebrew_cask homebrew_package homebrew_tap homebrew_update hostname http_request ifconfig inspec_input inspec_waiver inspec_waiver_file_entry ips_package kernel_module ksh launchd link locale log macos_pkg macos_userdefaults macosx_service macports_package mdadm mount msu_package notify_group ohai ohai_hint openbsd_package openssl_dhparam openssl_ec_private_key openssl_ec_public_key openssl_rsa_private_key openssl_rsa_public_key openssl_x509_certificate openssl_x509_crl openssl_x509_request osx_profile package pacman_package paludis_package perl plist portage_package powershell_package powershell_package_source powershell_script python reboot registry_key remote_directory remote_file rhsm_errata rhsm_errata_level rhsm_register rhsm_repo rhsm_subscription route rpm_package ruby ruby_block script selinux_boolean selinux_fcontext selinux_install selinux_login selinux_module selinux_permissive selinux_port selinux_state selinux_user service smartos_package snap_package solaris_package ssh_known_hosts_entry subversion sudo swap_file sysctl systemd_unit template timezone user user_ulimit windows_ad_join windows_audit_policy windows_auto_run windows_certificate windows_defender windows_defender_exclusion windows_dfs_folder windows_dfs_namespace windows_dfs_server windows_dns_record windows_dns_zone windows_env windows_feature windows_feature_dism windows_feature_powershell windows_firewall_profile windows_firewall_rule windows_font windows_package windows_pagefile windows_path windows_printer windows_printer_port windows_security_policy windows_service windows_share windows_shortcut windows_task windows_uac windows_update_settings windows_user_privilege windows_workgroup yum_package yum_repository zypper_package zypper_repository custom resources custom resource guide accumulators helpers partials migrating from definitions rest resource unified mode migration notes migrating from lwrps glossary extension apis handlers custom handlers handler dsl community handlers compliance dsl ohai plugins custom plugins community plugins reference chef client executable chef solo executable handler dsl ohai executable supermarket ctl client rb metadata rb policyfile rb solo rb chef infra client deprecations glossary troubleshooting chef documentation chef infra client chef infra client table of contents chef infra client is an agent that runs locally on every node that s under management by chef infra server chef infra client transforms your infrastructure into code by automatically configuring systems to match your desired state when chef infra client runs it performs all the steps required to bring a node into the expected state including registering and authenticating the node with chef infra server synchronizing cookbooks from chef infra server to the node compiling the resource collection by loading each of the required cookbooks including recipes attributes and all other dependencies taking the appropriate and required actions to configure the node based on recipes and attributes reporting summary information on the run to chef automate chef infra client components chef infra client works with key components to manage your infrastructure compliance phase the compliance phase is an integrated security and compliance feature that runs chef inspec profiles automatically as part of every chef infra client run this phase allows you to continuously audit your infrastructure for compliance with security policies and regulatory requirements without managing separate tools or processes for detailed information see about the compliance phase node a node represents any system that chef infra client manages whether it s a virtual machine container instance or physical server every node runs chef infra client and maintains its configuration state according to the policies you define cookbooks and recipes cookbooks contain the instructions recipes that tell chef infra client how to configure your systems recipes use resources to describe the desired state of system components like packages files and services run list the run list defines which cookbooks and recipes chef infra client should execute on a node and in what order you can customize run lists for different node types or environments ohai ohai is a system profiling tool that collects detailed information about your nodes including hardware details network configuration and operating system data chef infra client uses this information to make intelligent configuration decisions agentless agentless allows you to execute infra client runs on a target node over ssh without having chef infra client installed on the node for more details and setup instructions see the agentless documentation how chef infra client works chef infra client operates on a pull based model where nodes periodically contact chef infra server to retrieve their configuration policies this approach ensures that your infrastructure remains in the desired state even if individual nodes experience temporary disconnections or issues common use cases you can use chef infra client to automate infrastructure management tasks server provisioning automatically configure new servers with required software and settings application deployment deploy and configure applications across different environments security compliance enforce security policies and compliance requirements configuration drift prevention continuously check and correct configuration changes environment management maintain consistent configurations across development staging and production environments the chef infra client run a chef infra client run describes the steps chef infra client takes to configure a node when you run the chef client command the following diagram shows the various stages that occur during a chef infra client run during every chef infra client run the following happens get configuration data chef infra client gets process configuration data from the client rb file on the node and then gets node configuration data from ohai the node name is an important piece of configuration data chef infra client gets the node name from the node_name attribute in the client rb file or from ohai if ohai provides the node name it s typically the fqdn for the node which is always unique within an organization authenticate to chef infra server chef infra client authenticates to chef infra server using an rsa private key and the chef infra server api authentication with infra server requires the node name if this is the first chef infra client run for a node the chef validator generates an rsa private key get and rebuild the node object chef infra client pulls down the node object from chef infra server and then rebuilds it a node object contains the system attributes discovered by ohai the attributes set in policyfiles or cookbooks and the run list of cookbooks the first time chef infra client runs on a node it creates a node object from the default run list a node that hasn t yet had a chef infra client run won t have a node object or a chef infra server entry for a node object on any subsequent chef infra client runs the rebuilt node object also contains the run list from the previous chef infra client run expand the run list chef infra client expands the run list from the rebuilt node object and compiles a complete list of recipes in the exact order that they will be applied to the node synchronize cookbooks chef infra client requests all the cookbook files including recipes templates resources providers attributes and libraries that it needs for every action identified in the run list from chef infra server chef infra server responds to chef infra client with the complete list of files chef infra client compares the list of files to the files that already exist on the node from previous runs and then downloads a copy of every new or modified file from chef infra server reset node attributes all attributes in the rebuilt node object are reset all attributes from attribute files policyfiles and ohai are loaded attributes that are defined in attribute files are first loaded according to cookbook order for each cookbook attributes in the default rb file are loaded first and then additional attribute files if present are loaded in lexical sort order if attribute files are found within any cookbooks that are listed as dependencies in the metadata rb file these are loaded as well all attributes in the rebuilt node object are updated with the attribute data according to attribute precedence when all the attributes are updated the rebuilt node object is complete compile the resource collection chef infra client identifies each resource in the node object and builds the resource collection libraries are loaded first to ensure that all language extensions and ruby classes are available to all resources next attributes are loaded followed by custom resources finally all recipes are loaded in the order specified by the expanded run list this is the compile phase converge the node chef infra client configures the system based on the information that has been collected each resource is executed in the order identified by the run list and then by the order in which each resource is listed in each recipe each resource defines an action to run which configures a specific part of the system this process called convergence is also called the execution phase update the node object and process exception and report handlers when all the actions identified by resources in the resource collection have been completed and chef infra client finishes successfully chef infra client updates the node object on chef infra server with the node object built during the chef infra client run chef infra client will pull down this node object during the next chef infra client run this makes the node object and the data in the node object available for search chef infra client always checks the resource collection for the presence of exception and report handlers if any are present each one is processed appropriately get and run chef inspec compliance profiles after the chef infra client run finishes it begins the compliance phase which is a chef inspec run within the chef infra client chef inspec retrieves tests from either a legacy audit cookbook or a current inspec profile send or save compliance report when all the inspec tests finish running chef inspec checks the reporting handlers defined in the legacy audit cookbook or in a current inspec profile and processes them appropriately stop and wait for the next run when everything is configured and the chef infra client run is complete chef infra client stops and waits until the next time it s asked to run related content chef infra client executable chef infra server cookbooks nodes run lists next steps install chef workstation install infra client table of contents chef infra client chef infra client components compliance phase node cookbooks and recipes run list ohai agentless how chef infra client works common use cases the chef infra client run related content next steps was this page helpful yes no still stuck contact...
|
