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

Jump to bottom

[release/v1.7] do not put multiple identical tolerations on the CoreDNS deployment #3299

Merged
merged 1 commit into from
Jul 8, 2024
Merged

[release/v1.7] do not put multiple identical tolerations on the CoreDNS deployment #3299

merged 1 commit into from
Jul 8, 2024

Conversation

kubermatic-bot
Copy link
Contributor

This is an automated cherry-pick of #3297

/assign xrstf

Fix: do not put multiple identical tolerations on the CoreDNS deployment

@kubermatic-bot kubermatic-bot mentioned this pull request Jul 8, 2024
Merged
@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jul 8, 2024
@xrstf
Copy link
Contributor

xrstf commented Jul 8, 2024

/kind bug

@kubermatic-bot kubermatic-bot added kind/bug Categorizes issue or PR as related to a bug. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 8, 2024
@xrstf xrstf added the cherry-pick-approved Indicates a PR has been approved by release managers. label Jul 8, 2024
@kubermatic-bot kubermatic-bot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Jul 8, 2024
@kron4eg
Copy link
Member

kron4eg commented Jul 8, 2024

/lgtm
/approve

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

LGTM label has been added.

Git tree hash: c580d67e1755456e9f345b17729b64a70eeabc31

@kubermatic-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg

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 Jul 8, 2024
@kubermatic-triage-bot
Copy link

/retest
This bot automatically retries jobs that failed/flaked on approved PRs

Review the full test history

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

@kubermatic-bot kubermatic-bot merged commit a32adf9 into kubermatic:release/v1.7 Jul 8, 2024
13 checks passed
@kubermatic-bot kubermatic-bot deleted the cherry-pick-3297-to-release/v1.7 branch July 8, 2024 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@kron4eg kron4eg

@xrstf xrstf

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a PR has been approved by release managers. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@kubermatic-bot @xrstf @kron4eg @kubermatic-triage-bot