22sidebar_position : 15
33---
44
5- # 3. Instances
5+ # Instances
66
77Instances are a fundamental concept in ** KRO** that represent instances of
88ResourceGroups. They define the desired state of a set of resources, which KRO
3737 LOG_LEVEL : debug
3838` ` `
3939
40- :::tip The spec fields of an Instance correspond to the parameters defined in the
41- ResourceGroup. :::
40+ :::
41+
42+ tip The spec fields of an Instance correspond to the parameters defined in the
43+ ResourceGroup.
44+
45+ :::
4246
4347## The reconciliation loop
4448
@@ -53,8 +57,8 @@ KRO manages Instances through a continuous reconciliation process:
5357- **State Reconciliation**: KRO takes necessary actions to align the current
5458 state with the desired state. This may involve creating, updating, or deleting
5559 resources as needed.
56- - **Status Updates**: The Instance's status is updated to reflect the current state
57- of reconciliation and any issues encountered.
60+ - **Status Updates**: The Instance's status is updated to reflect the current
61+ state of reconciliation and any issues encountered.
5862- **Continuous Loop**: This process repeats regularly, ensuring the cluster
5963 state always converges towards the desired state defined in the Instance.
6064
@@ -69,16 +73,18 @@ KRO manages Instances through a continuous reconciliation process:
6973- **Auditability**: The Instance serves as a single source of truth for the
7074 application's desired state.
7175
72- :::tip Best Practices
76+ :::tip[ Best Practices]
7377
74- - Treat instances as declarative definitions of your application's desired state.
75- Use version control for your Instances to track changes over time.
78+ - Treat instances as declarative definitions of your application's desired
79+ state. Use version control for your Instances to track changes over time.
7680- Leverage labels and annotations in Instances for organization and filtering.
7781- Regularly review Instances to ensure they reflect current requirements.
7882- Use KRO's dry-run feature to preview reconciliation actions before applying
7983 changes to Instances.
80- - Monitor Instance statuses to understand the current state of your applications.
81- :::
84+ - Monitor Instance statuses to understand the current state of your
85+ applications.
86+
87+ :::
8288
8389## Common Status Fields
8490
@@ -93,8 +99,8 @@ detailed status information. Each condition represents a specific aspect of the
9399instance's state. Common conditions include:
94100
95101- **Ready**: Indicates whether the instance is fully reconciled and operational.
96- - **Progressing**: Shows if the instance is in the process of reaching the desired
97- state.
102+ - **Progressing**: Shows if the instance is in the process of reaching the
103+ desired state.
98104- **Degraded**: Signals that the instance is operational but not functioning
99105 optimally.
100106- **Error**: Indicates that an error has occurred during reconciliation.
@@ -121,8 +127,8 @@ status:
121127
122128### 2. State
123129
124- The State field provides a high-level summary of the instance's current status. It
125- is typically one of the following values:
130+ The State field provides a high-level summary of the instance's current status.
131+ It is typically one of the following values:
126132
127133- **Pending**: The instance is being processed, but resources are not yet fully
128134 created or configured.
@@ -140,6 +146,6 @@ status:
140146` ` `
141147
142148These common status fields provide users with a consistent and informative way
143- to check the health and state of their instances across different ResourceGroups.
144- They are essential for monitoring, troubleshooting, and automating operations
145- based on the status of KRO-managed resources.
149+ to check the health and state of their instances across different
150+ ResourceGroups. They are essential for monitoring, troubleshooting, and
151+ automating operations based on the status of KRO-managed resources.
0 commit comments