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.

Sign up for GitHub

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

docs: Use code format for env variables in upgrade guide #7683

Merged
merged 1 commit into from
Feb 4, 2025
Merged

docs: Use code format for env variables in upgrade guide #7683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/content/en/v1.0/upgrading/v1-migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -662,7 +662,7 @@ Revisit step 9 of the [upgrade procedure]({{< ref "#upgrading" >}}) and ensure t
* AMI Selector Terms has a new Alias field which can only be set by itself in `EC2NodeClass.Spec.AMISelectorTerms`
* Disruption Budgets by Reason was added to `NodePool.Spec.Disruption.Budgets`
* TerminationGracePeriod was added to `NodePool.Spec.Template.Spec`.
* LOG_OUTPUT_PATHS and LOG_ERROR_OUTPUT_PATHS environment variables added
* `LOG_OUTPUT_PATHS` and `LOG_ERROR_OUTPUT_PATHS` environment variables added
* API Rename: NodePool’s ConsolidationPolicy `WhenUnderutilized` is now renamed to `WhenEmptyOrUnderutilized`
* Behavior Changes:
* Expiration is now forceful and begins draining as soon as it’s expired. Karpenter does not wait for replacement capacity to be available before draining, but will start provisioning a replacement as soon as the node is expired and begins draining.
Expand All @@ -683,8 +683,8 @@ Revisit step 9 of the [upgrade procedure]({{< ref "#upgrading" >}}) and ensure t
* The taint used to mark nodes for disruption and termination changed from `karpenter.sh/disruption=disrupting:NoSchedule` to `karpenter.sh/disrupted:NoSchedule`. It is not recommended to tolerate this taint, however, if you were tolerating it in your applications, you'll need to adjust your taints to reflect this.
* Environment Variable Changes:
* Environment Variable Changes
* LOGGING_CONFIG, ASSUME_ROLE_ARN, ASSUME_ROLE_DURATION Dropped
* LEADER_ELECT renamed to DISABLE_LEADER_ELECTION
* `LOGGING_CONFIG, `ASSUME_ROLE_ARN`, `ASSUME_ROLE_DURATION` Dropped
* `LEADER_ELECT` renamed to `DISABLE_LEADER_ELECTION`
* `FEATURE_GATES.DRIFT=true` was dropped and promoted to Stable, and cannot be disabled.
* Users currently opting out of drift, disabling the drift feature flag will no longer be able to do so.
* Defaults changed:
Expand Down