-
Notifications
You must be signed in to change notification settings - Fork 9
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
Syncing latest changes from master for rook #583
Conversation
Reduce CRD size by removing some descriptions for things that (a) are long, (b) are repeated, and (c) are commong kubernetes types. Remove the `Status` field from VolumeClaimTemplates (a.k.a. PVCs) in types.go to remove all unnecessary status-related fields. Use `yq` to go through generated `crds.yaml` to strip out descriptions for well-known k8s types that are long and repeated where we can't remove them from types.go. This is mostly placement descriptions and volumeSource descriptions. The overall `crds.yaml` file is reduced to less than 60% of its original size. Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com> Signed-off-by: Redouane Kachach <rkachach@redhat.com> Co-authored-by: Blaine Gardner <blaine.gardner@ibm.com>
If the spec.mon.count is 5 or more, then create mon pdbs with maxUnavailable count as 2. We can afford to have more than 1 mons down while draining the nodes in this case. Signed-off-by: sp98 <sapillai@redhat.com>
Signed-off-by: Redouane Kachach <rkachach@redhat.com>
manifest: reduce CRD size by removing some descriptions
mon: set mon pdb max unavailable as 2 in case of 5 or more mons.
earlier, we were only checking the specs of networkFence to see if unfencing is done before proceeding with deletion but we should also check the status of networkFence before proceeding with deletion. Signed-off-by: subhamkrai <srai@redhat.com>
cephFs fencing needs more testing and bug fixes to make it in production. We tried multiple fixes but still it need more work. So, removing the cephfs networkFence realted code will rever this commit when we start working on this again. Signed-off-by: subhamkrai <srai@redhat.com>
For 1.14 release supporting squid is planned as well as DNS subdomain style access to RGW buckets. Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
docs: Add squid and bucket DNS subdomains to roadmap
The MDS resource requirements had an incorrect comment of the RGW component. Signed-off-by: Liang Zheng <zhengliang0901@gmail.com>
csi: disable cephFs network Fencing temporarily
mds: fix incorrect comment on crd resource requirements
Bumps the github-dependencies group with 1 update: [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go). Updates `github.com/aws/aws-sdk-go` from 1.50.20 to 1.50.25 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.50.20...v1.50.25) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Go is not cgroup aware and by default will set GOMAXPROCS to the number of available threads, regardless of whether it is within the allocated quota. This behaviour causes high amount of CPU throttling and degraded application performance. Fixes: rook#13815 Signed-off-by: Thomas Way <thomas@6f.io>
operator: use Linux container CPU quota
…dependencies-89693179d6 build(deps): bump the github-dependencies group with 1 update
Bumps [go.uber.org/zap](https://github.com/uber-go/zap) from 1.26.0 to 1.27.0. - [Release notes](https://github.com/uber-go/zap/releases) - [Changelog](https://github.com/uber-go/zap/blob/master/CHANGELOG.md) - [Commits](uber-go/zap@v1.26.0...v1.27.0) --- updated-dependencies: - dependency-name: go.uber.org/zap dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
….org/zap-1.27.0 build(deps): bump go.uber.org/zap from 1.26.0 to 1.27.0
removing extra space infront of 'network' commit tittle. Signed-off-by: shay1760 <rahulkrrai0302@gmail.com>
when comparing local ceph version with external cluster there is wrong log printing. Updating to print the right log message. Signed-off-by: shay1760 <rahulkrrai0302@gmail.com>
external: update logging when comparing ceph version
This commit uplifts prometheus operator version to v0.71.1. Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
…version-sunnat Bump Prometheus operator version to v0.71.1
@sp98 should we go ahead with the PR? given the CI error |
/approve |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: df-build-team, parth-gr 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 |
PR containing the latest commits from master branch