Skip to content

fix: docs double header in migration docs #2584

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.

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

Merged
merged 1 commit into from
Nov 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v2-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v1 to v2
description: Migrating from v1 to v2
layout: docs
permalink: /docs/v2-migration
---

# Migrating from v1 to v2

Version 2 of the framework introduces improvements, features and breaking changes for the APIs both
internal and user facing ones. The migration should be however trivial in most of the cases. For
detailed overview of all major issues until the release of
Expand Down
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v3-1-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v3 to v3.1
description: Migrating from v3 to v3.1
layout: docs
permalink: /docs/v3-1-migration
---

# Migrating from v3 to v3.1

## ReconciliationMaxInterval Annotation has been renamed to MaxReconciliationInterval

Associated methods on both the `ControllerConfiguration` class and annotation have also been
Expand Down
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v3-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v2 to v3
description: Migrating from v2 to v3
layout: docs
permalink: /docs/v3-migration
---

# Migrating from v2 to v3

Version 3 introduces some breaking changes to APIs, however the migration to these changes should be trivial.

## Reconciler
Expand Down
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v4-3-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v4.2 to v4.3
description: Migrating from v4.2 to v4.3
layout: docs
permalink: /docs/v4-3-migration
---

# Migrating from v4.2 to v4.3

## Condition API Change

In Workflows the target of the condition was the managed resource itself, not the target dependent resource.
Expand Down
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v4-4-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v4.3 to v4.4
description: Migrating from v4.3 to v4.4
layout: docs
permalink: /docs/v4-4-migration
---

# Migrating from v4.3 to v4.4

## API changes

### ConfigurationService
Expand Down
3 changes: 0 additions & 3 deletions docs/content/en/docs/migration/v4-5-migration.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,9 @@
---
title: Migrating from v4.4 to v4.5
description: Migrating from v4.4 to v4.5
layout: docs
permalink: /docs/v4-5-migration
---

# Migrating from v4.4 to v4.5

Version 4.5 introduces improvements related to event handling for Dependent Resources, more precisely the
[caching and event handling](https://javaoperatorsdk.io/docs/dependent-resources#caching-and-event-handling-in-kubernetesdependentresource)
features. As a result the Kubernetes resources managed using
Expand Down