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.

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

Fix missing new fields in AppDefs during KKP upgrades #13177

Merged
merged 2 commits into from Mar 14, 2024

Conversation

SimonTheLeg
Copy link
Member

@SimonTheLeg SimonTheLeg commented Mar 13, 2024

What this PR does / why we need it:
This makes the installer wait for the old webhooks to be gone before applying the AppDefs. This is important because in case of schema changes, the old mutation hooks would silently drop new fields.

Which issue(s) this PR fixes:
Fixes #13145

What type of PR is this?
/kind bug

Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

Signed-off-by: Simon Bein <simontheleg@gmail.com>
@kubermatic-bot kubermatic-bot added dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. docs/none Denotes a PR that doesn't need documentation (changes). release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Mar 13, 2024
@SimonTheLeg SimonTheLeg changed the title temp: fix missing appdef fields durig installation temp: fix missing appdef fields during installation Mar 13, 2024
@SimonTheLeg SimonTheLeg changed the title temp: fix missing appdef fields during installation wip: fix missing appdef fields during installation Mar 13, 2024
@kubermatic-bot kubermatic-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 13, 2024
@xrstf xrstf changed the title wip: fix missing appdef fields during installation Fix missing new fields in AppDefs during KKP upgrades Mar 13, 2024
@kubermatic-bot kubermatic-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 13, 2024
@xrstf xrstf added the code-freeze-approved Indicates a PR has been approved by release managers during code freeze. label Mar 13, 2024
@kubermatic-bot kubermatic-bot removed the do-not-merge/code-freeze Indicates that a PR should not merge because it has not been approved for code freeze yet. label Mar 13, 2024
@xrstf xrstf added this to the KKP 2.25 milestone Mar 13, 2024
Copy link
Member

@embik embik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 14, 2024
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: a814a8453dd9f5907b6a9e898bc15851b1e0ceb5

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 14, 2024
@kubermatic-bot kubermatic-bot merged commit d529549 into kubermatic:main Mar 14, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. code-freeze-approved Indicates a PR has been approved by release managers during code freeze. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Application catalog is missing icons after upgrading from KKP v2.24.4
4 participants