Postgres version update and minio client image add in values file #46 #62
Conversation
WalkthroughThe changes in this pull request involve updates to the Helm charts for both the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Outside diff range and nitpick comments (10)
charts/plane-ce/values.yaml (1)
Line range hint
39-62: Consider security improvements for sensitive valuesWhile reviewing the changes, I noticed that the file contains default passwords and secrets. Consider:
- Using external secrets management (e.g., Kubernetes Secrets, HashiCorp Vault)
- Documenting the need to change default credentials in production
This applies to:
pgdb_password: planeroot_password: passwordsecret_key: "60gp0byfz2dvffa45cxl20p1scy9xbpf6d8c5y0geejgkyp1b5"charts/plane-enterprise/values.yaml (1)
Line range hint
1-200: Security Advisory: Review default credentials in configurationWhile not directly related to the current changes, I noticed several default credentials and keys in the configuration:
- Default RabbitMQ credentials (user: plane, password: plane)
- Default PostgreSQL credentials (user: plane, password: plane)
- Default MinIO root credentials (user: admin, password: password)
- Hardcoded secret_key
Consider:
- Documenting that these are example values only
- Implementing a secret management solution
- Adding validation to prevent these default values in production environments
charts/plane-enterprise/templates/workloads/minio.stateful.yaml (2)
Line range hint
24-67: Consider adding production-ready configurationsWhile the StatefulSet configuration is functional, consider adding the following for production readiness:
- Resource limits and requests
- Readiness and liveness probes
- Security context
Add these configurations:
spec: containers: - image: {{ .Values.services.minio.image }} imagePullPolicy: Always name: {{ .Release.Name }}-minio + resources: + limits: + cpu: {{ .Values.services.minio.resources.limits.cpu | default "1" }} + memory: {{ .Values.services.minio.resources.limits.memory | default "2Gi" }} + requests: + cpu: {{ .Values.services.minio.resources.requests.cpu | default "200m" }} + memory: {{ .Values.services.minio.resources.requests.memory | default "512Mi" }} + livenessProbe: + httpGet: + path: /minio/health/live + port: 9000 + initialDelaySeconds: 30 + periodSeconds: 10 + readinessProbe: + httpGet: + path: /minio/health/ready + port: 9000 + initialDelaySeconds: 30 + periodSeconds: 10 + securityContext: + runAsNonRoot: true + runAsUser: 1000 + readOnlyRootFilesystem: true
Security concerns confirmed - Anonymous download access needs configuration control
The review comment's concerns are valid. The analysis reveals:
- Anonymous download access is configured unconditionally in both CE and Enterprise charts
- No configuration flag exists in values.yaml to control this behavior
- The
exit 0command masks potential errorsThe suggested improvements in the review comment are appropriate:
- Making anonymous download configurable via
.Values.services.minio.allowAnonymousDownload- Adding proper error handling with
|| exit 1- Removing unconditional
exit 0Additional findings:
- Both CE and Enterprise versions have this security concern
- The MinIO configuration is primarily for local setup (indicated by
local_setup: truein values.yaml)🔗 Analysis chain
Line range hint
69-123: Security and reliability concerns in bucket creation jobSeveral issues need attention:
- Setting anonymous download access might be too permissive for production
- Shell commands could fail silently due to
exit 0- No proper error handling for bucket creation
Consider these improvements:
args: - '-c' - >- /usr/bin/mc config host add plane-app-minio http://{{ .Release.Name }}-minio.{{ .Release.Namespace }}.svc.cluster.local:9000 "$AWS_ACCESS_KEY_ID" "$AWS_SECRET_ACCESS_KEY"; - /usr/bin/mc mb plane-app-minio/$AWS_S3_BUCKET_NAME; - /usr/bin/mc anonymous set download plane-app-minio/$AWS_S3_BUCKET_NAME; exit 0; + /usr/bin/mc mb plane-app-minio/$AWS_S3_BUCKET_NAME || exit 1; + {{- if .Values.services.minio.allowAnonymousDownload }} + /usr/bin/mc anonymous set download plane-app-minio/$AWS_S3_BUCKET_NAME || exit 1; + {{- end }}Also, verify if anonymous download access is really needed:
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check if anonymous access is used in the codebase rg -l 'anonymous.*download' --type yamlLength of output: 161
Script:
#!/bin/bash # Check the content of both files to understand the anonymous download usage rg -A 5 -B 5 'anonymous.*download' --type yamlLength of output: 2542
Script:
#!/bin/bash # Check if there are any values.yaml files that might configure this behavior fd "values.yaml" charts/Length of output: 88
Script:
#!/bin/bash # Check for any documentation about this configuration rg -i "anonymous.*download|public.*access" README.md docs/ 2>/dev/nullLength of output: 60
Script:
#!/bin/bash # Check the values.yaml files for any MinIO-related configurations rg -A 5 -B 5 "minio:" charts/plane-*/values.yamlLength of output: 1473
Script:
#!/bin/bash # Check if there are any frontend components that might require public access to MinIO rg -l "minio.*download|getSignedUrl|presignedUrl" --type ts --type jsLength of output: 220
charts/plane-ce/templates/workloads/minio.stateful.yaml (2)
Line range hint
25-77: Add essential security and reliability configurationsThe StatefulSet configuration should include:
- Resource limits and requests to prevent resource exhaustion
- Security context for running with minimal privileges
- Liveness and readiness probes for better reliability
Apply these improvements:
spec: template: spec: + securityContext: + fsGroup: 1000 + runAsNonRoot: true + runAsUser: 1000 containers: - image: {{ .Values.minio.image }} imagePullPolicy: {{ .Values.minio.pullPolicy | default "IfNotPresent" }} name: {{ .Release.Name }}-minio + resources: + limits: + cpu: "1" + memory: "2Gi" + requests: + cpu: "200m" + memory: "512Mi" + livenessProbe: + httpGet: + path: /minio/health/live + port: 9000 + initialDelaySeconds: 30 + readinessProbe: + httpGet: + path: /minio/health/ready + port: 9000 + initialDelaySeconds: 15
MinIO client image should use a fixed version tag
Using
latesttag for the MinIO client image (minio/mc:latest) is not recommended in production as it can lead to unexpected behavior and breaks reproducibility. Pin it to a specific version.Example fix:
- image_mc: minio/mc:latest + image_mc: minio/mc:RELEASE.2024-01-20T03-23-41ZThe PostgreSQL version compatibility is not a concern here since MinIO client only interacts with the MinIO server, not PostgreSQL.
🔗 Analysis chain
Line range hint
79-124: Improve bucket creation job reliabilityThe current implementation has several potential issues:
- The
exit 0at the end of the command will mask any errors in bucket creation- No retry mechanism for bucket creation failures
- Job pods might accumulate over time
Apply these improvements:
spec: + ttlSecondsAfterFinished: 100 template: spec: containers: - command: - /bin/sh args: - '-c' - >- /usr/bin/mc config host add plane-app-minio http://{{ .Release.Name }}-minio.{{ .Release.Namespace }}.svc.{{ .Values.env.default_cluster_domain | default "cluster.local" }}:9000 "$AWS_ACCESS_KEY_ID" "$AWS_SECRET_ACCESS_KEY" && - /usr/bin/mc mb plane-app-minio/$AWS_S3_BUCKET_NAME; - /usr/bin/mc anonymous set download plane-app-minio/$AWS_S3_BUCKET_NAME; exit 0; + /usr/bin/mc mb plane-app-minio/$AWS_S3_BUCKET_NAME && + /usr/bin/mc anonymous set download plane-app-minio/$AWS_S3_BUCKET_NAMEAlso, verify that the MinIO client image version is compatible with the updated PostgreSQL v15.7-alpine mentioned in the PR objectives.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check the default MinIO client image version in values rg "image_mc:" charts/plane-ce/values.yaml -A 1Length of output: 95
charts/plane-ce/questions.yml (1)
Line range hint
269-273: Update PostgreSQL version to match PR objectivesThe PR objectives specify updating PostgreSQL to v15.7-alpine, but the current default is still set to v15.5-alpine.
Apply this diff to update the PostgreSQL version:
- variable: postgres.image label: "Docker Image" type: string - default: "postgres:15.5-alpine" + default: "postgres:15.7-alpine" show_if: "postgres.local_setup=true"charts/plane-enterprise/questions.yml (1)
Line range hint
249-253: Update PostgreSQL version to match PR objectivesThe PR objectives mention updating PostgreSQL to v15.7-alpine, but this file still references v15.5-alpine. Please update the version to maintain consistency:
- variable: services.postgres.image label: "Docker Image" type: string - default: "registry.plane.tools/plane/postgres:15.5-alpine" + default: "registry.plane.tools/plane/postgres:15.7-alpine" show_if: "services.postgres.local_setup=true"charts/plane-ce/README.md (1)
125-125: Fix grammar: "setup" should be "set up" when used as a verb.The word "setup" is a noun, while "set up" is the correct verb form.
Apply this change:
-| minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to setup the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)| +| minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to set up the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)|🧰 Tools
🪛 LanguageTool
[grammar] ~125-~125: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment ofminio client. (...(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md (1)
150-150: Fix grammatical error in the descriptionThe word "setup" is being used as a verb, but it should be "set up" when used as a verb.
-| services.minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to setup the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)| +| services.minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to set up the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)|🧰 Tools
🪛 LanguageTool
[grammar] ~150-~150: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment ofminio client. (...(NOUN_VERB_CONFUSION)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (10)
charts/plane-ce/Chart.yaml(1 hunks)charts/plane-ce/README.md(1 hunks)charts/plane-ce/questions.yml(1 hunks)charts/plane-ce/templates/workloads/minio.stateful.yaml(1 hunks)charts/plane-ce/values.yaml(2 hunks)charts/plane-enterprise/Chart.yaml(1 hunks)charts/plane-enterprise/README.md(1 hunks)charts/plane-enterprise/questions.yml(1 hunks)charts/plane-enterprise/templates/workloads/minio.stateful.yaml(1 hunks)charts/plane-enterprise/values.yaml(2 hunks)
✅ Files skipped from review due to trivial changes (2)
- charts/plane-ce/Chart.yaml
- charts/plane-enterprise/Chart.yaml
🧰 Additional context used
🪛 LanguageTool
charts/plane-ce/README.md
[grammar] ~125-~125: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md
[grammar] ~150-~150: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
🔇 Additional comments (7)
charts/plane-ce/values.yaml (1)
39-39: PostgreSQL version update looks good, verify changelog
The update to PostgreSQL 15.7-alpine is appropriate as it's the latest stable minor version in the 15.x series.
Let's verify the changelog and any potential breaking changes:
✅ Verification successful
Let me try a different approach to fetch the changelog information:
The previous attempt to fetch release notes directly didn't work well. Let's search the repository for any upgrade notes, version constraints, or changelog information that might indicate potential issues with the PostgreSQL version update.
PostgreSQL version update from 15.5 to 15.7 is safe to proceed
The update from PostgreSQL 15.5 to 15.7 is a minor version increment within the same major version (15.x). Minor version updates in PostgreSQL are backward compatible and typically contain only bug fixes and security patches. Since this is a patch release update within the stable 15.x series, and the image is from the official PostgreSQL repository, it's safe to proceed with this change.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Fetch PostgreSQL 15.7 release notes and compare with 15.5
curl -s https://www.postgresql.org/docs/release/15.7/ | grep -A 10 "Release Notes"
curl -s https://www.postgresql.org/docs/release/15.5/ | grep -A 10 "Release Notes"
Length of output: 5513
Script:
#!/bin/bash
# Search for any upgrade notes or migration guides in the repository
rg -i "postgresql.*15\.[567]|upgrade.*postgres" --type md
fd -e md -e txt UPGRADE
fd -e md -e txt CHANGELOG
# Check if there are any specific PostgreSQL version requirements or constraints
rg -i "postgres.*version|postgresql.*version" --type yaml
Length of output: 173
charts/plane-enterprise/templates/workloads/minio.stateful.yaml (2)
Line range hint 3-23: LGTM: Service configuration follows best practices
The Service configuration is well-structured with:
- Clear port naming for both MinIO API and console
- Configurable clusterIP through
assign_cluster_ipvalue - Consistent labeling scheme
118-118: Verify MinIO client image configuration
The change to use a templated image value is good, but ensure the default value is set in values.yaml.
✅ Verification successful
MinIO client image configuration is properly set
The default value for services.minio.image_mc is correctly defined in values.yaml as minio/mc:latest.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if image_mc is properly defined in values.yaml
rg "image_mc:" charts/plane-enterprise/values.yaml -A 1
Length of output: 105
charts/plane-ce/templates/workloads/minio.stateful.yaml (1)
Line range hint 1-24: Verify the implications of local_setup condition
The entire MinIO configuration is wrapped in a minio.local_setup condition. Please ensure that:
- This aligns with the intended deployment strategy for non-local environments
- Documentation clearly states this limitation
- Alternative MinIO configuration exists for production deployments
The headless service configuration (when assign_cluster_ip is false) is correct for StatefulSet usage.
✅ Verification successful
Local setup condition is properly documented and has alternative configurations
The MinIO configuration wrapped in local_setup condition is intentional and well-documented. The README.md clearly explains:
- The local setup option deploys MinIO within Kubernetes
- Alternative configuration exists using external S3-compatible storage when
minio.local_setup=false - Required configuration parameters for both scenarios are documented:
- For local setup: image, volume size, credentials, etc.
- For external setup: AWS credentials, endpoint URL, region, etc.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if there are alternative MinIO configurations for non-local setups
rg -l "kind: (Service|StatefulSet)" charts/ | grep -i "minio"
# Check if the limitation is documented
rg -i "local_setup|minio" charts/plane-ce/README.md
Length of output: 6802
charts/plane-ce/questions.yml (1)
415-419: LGTM: MinIO client image configuration added correctly
The new configuration for MinIO client Docker image is well-structured and consistent with other image configurations in the file. It correctly:
- Uses conditional showing based on
minio.local_setup - Provides a sensible default value
- Has clear labeling
charts/plane-ce/README.md (1)
125-125: LGTM: MinIO client image configuration is well documented.
The new configuration setting minio.image_mc is properly documented with its purpose and requirements, aligning with the PR objectives.
🧰 Tools
🪛 LanguageTool
[grammar] ~125-~125: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md (1)
150-150: Documentation for MinIO client image looks good!
The addition of the services.minio.image_mc configuration setting is well-documented with clear requirements and usage instructions.
🧰 Tools
🪛 LanguageTool
[grammar] ~150-~150: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
| @@ -59,6 +59,7 @@ rabbitmq: | |||
|
|
|||
| minio: | |||
| image: minio/minio:latest | |||
| image_mc: minio/mc:latest | |||
There was a problem hiding this comment.
Avoid using 'latest' tag for MinIO client image
While the addition of the MinIO client image configuration is good, using the 'latest' tag in production environments is not recommended as it:
- Makes deployments non-deterministic
- Can cause unexpected behavior during updates
- Makes rollbacks difficult
Consider using a specific version tag instead:
- image_mc: minio/mc:latest
+ image_mc: minio/mc:RELEASE.2024-03-25T16-41-14Z📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| image_mc: minio/mc:latest | |
| image_mc: minio/mc:RELEASE.2024-03-25T16-41-14Z |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
charts/plane-ce/README.md (2)
125-125: Fix grammar in documentation.The documentation for the MinIO Client image configuration is clear and helpful. However, there's a minor grammar issue:
-| minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to setup the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)| +| minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to set up the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)|🧰 Tools
🪛 LanguageTool
[grammar] ~125-~125: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment ofminio client. (...(NOUN_VERB_CONFUSION)
80-80: Fix grammar in documentation.Similar grammar correction needed for PostgreSQL documentation:
-| postgres.image | postgres:15.7-alpine | | Using this key, user must provide the docker image name to setup the stateful deployment of `postgres`. (must be set when `postgres.local_setup=true`)| +| postgres.image | postgres:15.7-alpine | | Using this key, user must provide the docker image name to set up the stateful deployment of `postgres`. (must be set when `postgres.local_setup=true`)|🧰 Tools
🪛 LanguageTool
[grammar] ~80-~80: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment ofpostgres. ...(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md (1)
109-109: Fix grammar: "setup" should be "set up" when used as a verbThe word "setup" is used as a verb in these lines, but it should be "set up" (two words) when used as a verb. "Setup" (one word) is correct only when used as a noun.
Apply these corrections:
-| services.postgres.image | registry.plane.tools/plane/postgres:15.7-alpine | | Using this key, user must provide the docker image name to setup the stateful deployment of `postgres`. (must be set when `services.postgres.local_setup=true`)| +| services.postgres.image | registry.plane.tools/plane/postgres:15.7-alpine | | Using this key, user must provide the docker image name to set up the stateful deployment of `postgres`. (must be set when `services.postgres.local_setup=true`)| -| services.minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to setup the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)| +| services.minio.image_mc | minio/mc:latest | | Using this key, user must provide the docker image name to set up the job deployment of `minio client`. (must be set when `services.minio.local_setup=true`)|Also applies to: 150-150
🧰 Tools
🪛 LanguageTool
[grammar] ~109-~109: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment ofpostgres. ...(NOUN_VERB_CONFUSION)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (4)
charts/plane-ce/README.md(2 hunks)charts/plane-ce/questions.yml(11 hunks)charts/plane-enterprise/README.md(2 hunks)charts/plane-enterprise/questions.yml(5 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
- charts/plane-ce/questions.yml
- charts/plane-enterprise/questions.yml
🧰 Additional context used
🪛 LanguageTool
charts/plane-ce/README.md
[grammar] ~80-~80: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment of postgres. ...
(NOUN_VERB_CONFUSION)
[grammar] ~125-~125: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md
[grammar] ~109-~109: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment of postgres. ...
(NOUN_VERB_CONFUSION)
[grammar] ~150-~150: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
🔇 Additional comments (3)
charts/plane-ce/README.md (1)
80-80: LGTM! Verify PostgreSQL version compatibility.
The PostgreSQL version update to 15.7-alpine is documented correctly. This minor version update should maintain backward compatibility.
✅ Verification successful
PostgreSQL 15.7-alpine version update is safe to proceed
The verification confirms:
- PostgreSQL 15.7-alpine image is officially available on Docker Hub and actively maintained
- No breaking changes or incompatibilities were found in the version update from 15.5 to 15.7
- The image is available for multiple architectures including amd64, arm64, and others
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify PostgreSQL version compatibility by checking release notes and migration guides
# Check if there are any breaking changes in PostgreSQL 15.7 release notes
curl -s https://www.postgresql.org/docs/release/15.7/ | grep -i "breaking\|incompatible"
# Check if the image exists on Docker Hub
curl -s https://hub.docker.com/v2/repositories/library/postgres/tags/15.7-alpine
Length of output: 5595
🧰 Tools
🪛 LanguageTool
[grammar] ~80-~80: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment of postgres. ...
(NOUN_VERB_CONFUSION)
charts/plane-enterprise/README.md (2)
150-150: LGTM: MinIO client image configuration added
The addition of the MinIO client image configuration is well documented with clear explanation of its purpose and requirement conditions.
🧰 Tools
🪛 LanguageTool
[grammar] ~150-~150: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the job deployment of minio client. (...
(NOUN_VERB_CONFUSION)
109-109: Verify PostgreSQL version compatibility
The PostgreSQL version update from 15.5-alpine to 15.7-alpine looks good. This is a minor version update that should maintain backward compatibility.
✅ Verification successful
PostgreSQL version update is consistently applied
The version update from 15.5-alpine to 15.7-alpine has been consistently applied across all relevant configuration files in both the enterprise and community edition charts:
charts/plane-enterprise/values.yamlcharts/plane-enterprise/questions.ymlcharts/plane-enterprise/README.mdcharts/plane-ce/values.yamlcharts/plane-ce/questions.ymlcharts/plane-ce/README.md
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify PostgreSQL version references across the codebase
# Check for any hardcoded PostgreSQL version references that might need updating
# Search for PostgreSQL version references
rg -i "postgres.*15\.[57]"
# Check for potential version constraints in deployment files
fd -e yaml -e yml | xargs rg -i "postgres.*version"
Length of output: 901
🧰 Tools
🪛 LanguageTool
[grammar] ~109-~109: The word “setup” is a noun. The verb is spelled with a white space.
Context: ...r must provide the docker image name to setup the stateful deployment of postgres. ...
(NOUN_VERB_CONFUSION)
Changes:
PG Version - v15.7-alpine
MinIO Client image using values.yml file
Summary by CodeRabbit
New Features
Updates
plane-ceandplane-enterpriseapplications.15.7-alpine.Documentation