Syncing latest changes from upstream master for rook #695
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
Signed-off-by: Artem Torubarov <artem.torubarov@clyso.com>
Signed-off-by: Artem Torubarov <artem.torubarov@clyso.com>
Bumps [wagoid/commitlint-github-action](https://github.com/wagoid/commitlint-github-action) from 6.0.1 to 6.0.2. - [Changelog](https://github.com/wagoid/commitlint-github-action/blob/master/CHANGELOG.md) - [Commits](wagoid/commitlint-github-action@v6.0.1...v6.0.2) --- updated-dependencies: - dependency-name: wagoid/commitlint-github-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
target placement design doc
Bumps the github-dependencies group with 3 updates: [github.com/IBM/keyprotect-go-client](https://github.com/IBM/keyprotect-go-client), [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) and [github.com/k8snetworkplumbingwg/network-attachment-definition-client](https://github.com/k8snetworkplumbingwg/network-attachment-definition-client). Updates `github.com/IBM/keyprotect-go-client` from 0.14.3 to 0.15.1 - [Release notes](https://github.com/IBM/keyprotect-go-client/releases) - [Changelog](https://github.com/IBM/keyprotect-go-client/blob/master/CHANGELOG.md) - [Commits](IBM/keyprotect-go-client@v0.14.3...v0.15.1) Updates `github.com/aws/aws-sdk-go` from 1.55.3 to 1.55.5 - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Commits](aws/aws-sdk-go@v1.55.3...v1.55.5) Updates `github.com/k8snetworkplumbingwg/network-attachment-definition-client` from 1.7.0 to 1.7.1 - [Release notes](https://github.com/k8snetworkplumbingwg/network-attachment-definition-client/releases) - [Commits](k8snetworkplumbingwg/network-attachment-definition-client@v1.7.0...v1.7.1) --- updated-dependencies: - dependency-name: github.com/IBM/keyprotect-go-client dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-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/k8snetworkplumbingwg/network-attachment-definition-client dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
This commit adds example yamls for block volume mode. Signed-off-by: Rakshith R <rar@redhat.com>
csi: add pvc & pod yamls for block volume mode
…oid/commitlint-github-action-6.0.2 build(deps): bump wagoid/commitlint-github-action from 6.0.1 to 6.0.2
…dependencies-49fcb8191a build(deps): bump the github-dependencies group with 3 updates
adding code changes,rbac changes required for create the new Ceph-CSI operator CR named cephCluster in api group 'csi.ceph.io'. Signed-off-by: subhamkrai <srai@redhat.com>
adding changes to create CSI-operator config CR based on every radosnamesapce and subvolumegroup. Signed-off-by: subhamkrai <srai@redhat.com>
Signed-off-by: subhamkrai <srai@redhat.com>
df-build-team
force-pushed
the
sync_us--master
branch
from
83b3fb3
to
89f29a4
Compare
adding the CSI-operator manifest files inside rook repo naming deploy/examples/csi-operator-manifests.yaml. Also, let's skip running any lint check on file `deploy/examples/csi-operator.yaml` as this is owned by CSI-operator. Signed-off-by: subhamkrai <srai@redhat.com>
adding annotation to existing CSI driver resource so that csi-operator can take ownership of existing CSI driver resources. Signed-off-by: subhamkrai <srai@redhat.com>
adding unit test for csi-op resources and also fixing small pointer issue with this commit. Signed-off-by: subhamkrai <srai@redhat.com>
|
/test unit |
For the specification see: <https://github.com/rook/rook/blob/master/design/ceph/object/swift-and-keystone-integration.md> * extend the API object specs for swift and keystone integration * adapt rgw to the new go-ceph version - The parameter lists of the API call have changes, as parameters ignored by the RGW Admin Ops API are no longer serialized, therefore the mock has to be adapted. - There is now validation for the user keys that are passed to the User get API, therefore things failed when we had empty keys in our User proxy object. * expand the reconcile loop for the swift and keystone integration * fix minor mistakes in design document * add env var to pass extra args to minikube Minikube decides CPU cores and memory automatically based on the available resources on the machine which may be insufficient to run rook. This commit adds an environment variable to add arbitrary arguments to the minikube command, so both can be specified if desired. * integration tests for swift and keystone The new integration of swift or s3 and keystone support by rook does not have any integration tests yet. This commit introduces integration tests for swift and keystone. The tests are done against a minimal keystone setup (keystone container image from Yaook-project (https://yaook.cloud), sqlite as database backend, cert-manager and trust-manager for test certificate setup). To prevent hardcoded credentials, passwords are generated by the tests. The integration tests use the openstack client (keystone- and swift-functionality) (https://docs.openstack.org/ python-openstackclient/ latest/). This was a concious design decision to use client tooling as close as possible to the end user instead of using other go-libraries (such as gophercloud). * add documentation on swift and keystone Currently there is no documentation on the use of Swift to access an object store as well as the use of OpenStack keystone for authentication. This commit adds documentation on the use of Swift and OpenStack keystone, as well as CRD-related documentation and an example setup. * add integration tests for S3 via keystone This commit introduces integration tests for s3 and keystone. The tests are run against the same minimal keystone setup that the tests for swift and keystone use. The integration tests use the aws s3 client to use client tooling as close as possible to the end user instead of using other go-libraries. Co-authored-by: Jan Klippel <jan.klippel@uhurutec.com> Co-authored-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com> Signed-off-by: Sebastian Riese <sebastian.riese@cloudandheat.com> Signed-off-by: Jan Klippel <jan.klippel@uhurutec.com> Signed-off-by: Silvio Ankermann <silvio.ankermann@cloudandheat.com>
…onfig csi: add csi-operator operator config cr
rgw: implement support for authentication using keystone for s3 and swift
Signed-off-by: Zuhair AlSader <zuhair@devzero.io>
subhamkrai
added
the
do-not-merge
|
/hold This pr contains new csi-operator changes, let's wait for rook#14551 to be stable then backport csi-operator changes to ds |
openshift-ci
bot
added
the
do-not-merge/hold
This doesn't affect downstream until rook#14551 is merged, right? So it seems harmless to continue merging the resync. |
docs: fix affinity docs in operator chart
df-build-team
force-pushed
the
sync_us--master
branch
from
8e3d24b
to
b7e5f8e
Compare
added 2 commits
August 11, 2024 04:04
…-master Signed-off-by: Ceph Jenkins <ceph-jenkins@redhat.com>
add generated csv changes Signed-off-by: Ceph Jenkins <ceph-jenkins@redhat.com>
df-build-team
force-pushed
the
sync_us--master
branch
from
b7e5f8e
to
18a9523
Compare
subhamkrai
approved these changes
Aug 12, 2024
|
/approve |
subhamkrai
added
approved
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: df-build-team, subhamkrai 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 |
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