Syncing latest changes from upstream master for rook #573
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds the default crush location labels to csi configMap. Signed-off-by: Praveen M <[email protected]>
This commit resolves the issue where the netNamespaceFilePath was not being updated for all clusterIDs present in the csi configMap. Signed-off-by: Praveen M <[email protected]>
Signed-off-by: Michael Adam <[email protected]>
Fixes: rook#13692 Since the introduction of the "host" network provider, the legacy "hostNetwork" setting is intended to be used only in combination with the default network provider (""), but the code did not enforce this. This change adds the required validation checks to throw errors in invalid constellations. These checks are added both in the operator's input validation code and as kubernetes x-validation admission policies in the Cepcluster CRD. Signed-off-by: Michael Adam <[email protected]>
Mgr sidecar was using a privileged security context because it needed to create the /var/lib/rook directory, generate the config on it, and then copy it to the /etc/ceph directory. This change creates empty directories on /var/lib/rook and /etc/ceph so the mgr sidecar can use them, removing the need for using a privileged security context. Fixes: rook#13719 Signed-off-by: Redouane Kachach <[email protected]>
csi: update netNamespaceFilePath for all clusterIDs
Disallow legacy hostNetwork together with non-default provider
mgr: remove privileged security context from mgr sidecar container
since networkFence is a cluster-based resource so that we don't need the namespace and ownerReferences as it cause garbage-collector errors. Also, now we create the networkFence with clusteUID label so when doing cleanup we match the cephCluster uid and networkFence label clusterUID. Signed-off-by: subhamkrai <[email protected]>
upgrading minimum kubernetes supported version to v1.24.17 and also upgrading other kubernetes version to their latest respective version. Signed-off-by: subhamkrai <[email protected]>
ci: upgrade min k8s supported version to 1.24.17
…etworkFence core: Delete networkFence CRs during cluster removal
Bumps the github-dependencies group with 2 updates: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) and [github.com/hashicorp/vault/api](https://github.com/hashicorp/vault). Updates `github.com/aws/aws-sdk-go` from 1.50.12 to 1.50.15 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.50.12...v1.50.15) Updates `github.com/hashicorp/vault/api` from 1.11.0 to 1.12.0 - [Release notes](https://github.com/hashicorp/vault/releases) - [Changelog](https://github.com/hashicorp/vault/blob/main/CHANGELOG.md) - [Commits](hashicorp/vault@v1.11.0...v1.12.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies - dependency-name: github.com/hashicorp/vault/api dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>
…dependencies-991846f5e8 build(deps): bump the github-dependencies group with 2 updates
|
@df-build-team: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: df-build-team, travisn The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR containing the latest commits from upstream master branch