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] Use env to determine cluster name used by OpenStack CCM and CSI, increase memory limits and requests for cluster-autoscaler #2979

Merged
merged 2 commits into from
Dec 13, 2023
Merged

[release/v1.7] Use env to determine cluster name used by OpenStack CCM and CSI, increase memory limits and requests for cluster-autoscaler #2979

merged 2 commits into from
Dec 13, 2023

Conversation

kubermatic-bot
Copy link
Contributor

This is an automated cherry-pick of #2978

/assign xmudrii

- [ACTION REQUIRED] Use the `CLUSTER_NAME` environment variable from the OpenStack CCM pods to determine the current cluster name used by the OpenStack CCM. Fixes a regression where cluster name was changed to `kubernetes` upon running `kubeone apply` two or more times after upgrading from KubeOne 1.6 to KubeOne 1.7. Please check the known issues document to find if you're affected by this issue and what steps you need to take if you're affected
- Increase the memory requests and limits from 300Mi to 600Mi for cluster-autoscaler

@xmudrii
Use env to determine cluster name used by OpenStack CCM and CSI
1ecdcd6 
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@xmudrii
Increase memory requests and limits for cluster-autoscaler
8cf0988 
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
@kubermatic-bot kubermatic-bot mentioned this pull request Dec 13, 2023
Merged
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.7 milestone Dec 13, 2023
@kubermatic-bot kubermatic-bot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. 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 Dec 13, 2023
xmudrii
xmudrii approved these changes Dec 13, 2023
View reviewed changes
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

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

/kind bug regression
/lgtm
/approve

@kubermatic-bot kubermatic-bot added kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. kind/regression Categorizes issue or PR as related to a regression from a prior release. labels Dec 13, 2023
@kubermatic-bot
Copy link
Contributor Author

LGTM label has been added.

Git tree hash: da6345599b3b4e4eac9ed5dbb47619079f969a37

@kubermatic-bot kubermatic-bot removed the do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Dec 13, 2023
@kubermatic-bot
Copy link
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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 Dec 13, 2023
@xmudrii xmudrii added the cherry-pick-approved Indicates a PR has been approved by release managers. label Dec 13, 2023
@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 Dec 13, 2023
@kubermatic-bot kubermatic-bot merged commit 71c3590 into kubermatic:release/v1.7 Dec 13, 2023
13 checks passed
@kubermatic-bot kubermatic-bot deleted the cherry-pick-2978-to-release/v1.7 branch December 13, 2023 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@xmudrii xmudrii xmudrii approved these changes

Assignees

@xmudrii xmudrii

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. kind/regression Categorizes issue or PR as related to a regression from a prior release. lgtm Indicates that a PR is ready to be merged. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
KubeOne 1.7
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@kubermatic-bot @xmudrii