Skip to content

Commit

Permalink
docs: Update Drift fields include correct CRD path (#5486)
Browse files Browse the repository at this point in the history
  • Loading branch information
engedaam authored Jan 22, 2024
1 parent 2cb725d commit e98dddb
Show file tree
Hide file tree
Showing 4 changed files with 40 additions and 44 deletions.
21 changes: 10 additions & 11 deletions website/content/en/docs/concepts/disruption.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,25 +126,24 @@ In special cases, drift can correspond to multiple values and must be handled di
##### NodePool
| Fields |
|----------------|
| Requirements |
| spec.template.spec.requirements |
##### EC2NodeClass
| Fields |
|-------------------------------|
| Subnet Selector Terms |
| Security Group Selector Terms |
| AMI Selector Terms |
| spec.subnetSelectorTerms |
| spec.securityGroupSelectorTerms |
| spec.amiSelectorTerms |
#### Behavioral Fields
Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
__Behavioral Fields__
- Weight
- Limits
- ConsolidationPolicy
- ConsolidateAfter
- ExpireAfter
---
##### NodePool
| Fields |
|----------------|
| spec.weight |
| spec.limits |
| spec.disruption.* |
Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
Expand Down
21 changes: 10 additions & 11 deletions website/content/en/preview/concepts/disruption.md
Original file line number Diff line number Diff line change
Expand Up @@ -138,25 +138,24 @@ In special cases, drift can correspond to multiple values and must be handled di
##### NodePool
| Fields |
|----------------|
| Requirements |
| spec.template.spec.requirements |
##### EC2NodeClass
| Fields |
|-------------------------------|
| Subnet Selector Terms |
| Security Group Selector Terms |
| AMI Selector Terms |
| spec.subnetSelectorTerms |
| spec.securityGroupSelectorTerms |
| spec.amiSelectorTerms |
#### Behavioral Fields
Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
__Behavioral Fields__
- Weight
- Limits
- ConsolidationPolicy
- ConsolidateAfter
- ExpireAfter
---
##### NodePool
| Fields |
|---------------------|
| spec.weight |
| spec.limits |
| spec.disruption.* |
Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
Expand Down
21 changes: 10 additions & 11 deletions website/content/en/v0.32/concepts/disruption.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,25 +126,24 @@ In special cases, drift can correspond to multiple values and must be handled di
##### NodePool
| Fields |
|----------------|
| Requirements |
| spec.template.spec.requirements |
##### EC2NodeClass
| Fields |
|-------------------------------|
| Subnet Selector Terms |
| Security Group Selector Terms |
| AMI Selector Terms |
| spec.subnetSelectorTerms |
| spec.securityGroupSelectorTerms |
| spec.amiSelectorTerms |
#### Behavioral Fields
Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
__Behavioral Fields__
- Weight
- Limits
- ConsolidationPolicy
- ConsolidateAfter
- ExpireAfter
---
##### NodePool
| Fields |
|----------------|
| spec.weight |
| spec.limits |
| spec.disruption.* |
Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
Expand Down
21 changes: 10 additions & 11 deletions website/content/en/v0.33/concepts/disruption.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,25 +126,24 @@ In special cases, drift can correspond to multiple values and must be handled di
##### NodePool
| Fields |
|----------------|
| Requirements |
| spec.template.spec.requirements |
##### EC2NodeClass
| Fields |
|-------------------------------|
| Subnet Selector Terms |
| Security Group Selector Terms |
| AMI Selector Terms |
| spec.subnetSelectorTerms |
| spec.securityGroupSelectorTerms |
| spec.amiSelectorTerms |
#### Behavioral Fields
Behavioral Fields are treated as over-arching settings on the NodePool to dictate how Karpenter behaves. These fields don’t correspond to settings on the NodeClaim or instance. They’re set by the user to control Karpenter’s Provisioning and disruption logic. Since these don’t map to a desired state of NodeClaims, __behavioral fields are not considered for Drift__.
__Behavioral Fields__
- Weight
- Limits
- ConsolidationPolicy
- ConsolidateAfter
- ExpireAfter
---
##### NodePool
| Fields |
|----------------|
| spec.weight |
| spec.limits |
| spec.disruption.* |
Read the [Drift Design](https://github.com/aws/karpenter-core/blob/main/designs/drift.md) for more.
Expand Down

0 comments on commit e98dddb

Please sign in to comment.