Skip to content

Conversation

@balasankarc
Copy link
Collaborator

@balasankarc balasankarc commented Aug 28, 2025

Expose bucket name and project ID to configure GCS as object storage backend for Pulp.

Ideally, we should support mounting a credentials file to the pods and/or setting GOOGLE_APPLICATION_CREDENTIALS env variable (to point to it). This PR does not do that, and only enables GCS support using the Application Default Credentials.

closes #794

@openshift-ci
Copy link

openshift-ci bot commented Aug 28, 2025

Hi @balasankarc. Thanks for your PR.

I'm waiting for a pulp member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@balasankarc balasankarc force-pushed the add-gcs-support branch 2 times, most recently from ecbb7f5 to 0b64f85 Compare September 9, 2025 08:07
@balasankarc balasankarc changed the title [WIP] Add support for GCS Object Storage Add support for GCS Object Storage Sep 9, 2025
`
*pulpSettings += fmt.Sprintln("}")
}

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The logic above is essentially copied from how we do S3 secrets below.

Expose bucket name to configure GCS as object storage backend for Pulp.
Also expose optional fields like `iam_sign_blob`, `querystring_auth`,
and `file_overwrite`.

closes pulp#794

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
@balasankarc
Copy link
Collaborator Author

@ipanova @git-hyagi This should be now ready for review. I didn't see any unit tests existing for Azure/S3, so I haven't done anything for GCS either.

@git-hyagi
Copy link
Collaborator

/ok-to-test

Copy link
Collaborator

@git-hyagi git-hyagi left a comment

Choose a reason for hiding this comment

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

Hi @balasankarc

Thank you for your contribution!!

I didn't see any unit tests existing for Azure/S3, so I haven't done anything for GCS either.

Yeah, our unit tests are indeed lacking additional coverage and unfortunately we didn't have time to work on it yet.

The CI is failing in some steps, but I don't think they are related to this change (I will investigate and fix them later, in another PR).

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Sep 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: balasankarc, git-hyagi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@git-hyagi git-hyagi merged commit 4ed786e into pulp:main Sep 11, 2025
20 of 30 checks passed
@balasankarc
Copy link
Collaborator Author

@git-hyagi Will it be possible to tag a new release with this change? Thanks.

/cc @bmbouter

@openshift-ci openshift-ci bot requested a review from bmbouter September 14, 2025 05:32
@balasankarc balasankarc deleted the add-gcs-support branch September 14, 2025 05:43
@git-hyagi
Copy link
Collaborator

Hi @balasankarc,

Sorry for the delayed response!
Version 1.1.0 (https://github.com/pulp/pulp-operator/tree/1.1.0) released.

@balasankarc
Copy link
Collaborator Author

@git-hyagi
Copy link
Collaborator

hmm ... I believe you are right. I probably messed up with the release versioning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

As a user I can have Google Cloud storage as object storage

2 participants