fsGroup in postgres deployment

[modassarrana89]

File write permission issue happens when we select ceph as default storage for both power & Z . To resolve the issue , added fsGroup in the postgres Deployment

Tested with the changes & is working fine on IBMZ. Need to be verified on Power & x86

[modassarrana89]

@dmage Please review & ask QE team to verify the same on x86
@yussufsh Added fsGroup . please ask your team to verify on Power

[deshpandevlab]

@sourcery-ai guide

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds the fsGroup field to the securityContext of the postgres deployments. This ensures that the postgres pods have the correct permissions to write to the shared storage, resolving file permission issues when using ceph as the default storage.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added fsGroup to the securityContext of the postgres deployments.	Added securityContext with fsGroup: 2000 to the postgres deployment. The fsGroup ensures that all processes within the pod have the correct group ID, allowing them to access the shared storage.	kustomize/components/clairpostgres/postgres.deployment.yaml kustomize/components/postgres/postgres.deployment.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[openshift-ci]

@modassarrana89: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ocp-latest-e2e	9048363	link	true	/test ocp-latest-e2e

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.