Description
Please ensure you do the following when reporting a bug:
- Provide a concise description of what the bug is.
- Provide information about your environment.
- Provide clear steps to reproduce the bug.
- Attach applicable logs. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data.
- Ensure any code / output examples are properly formatted for legibility.
Note that some logs needed to troubleshoot may be found in the /pgdata/<CLUSTERNAME>/pg_log directory on your Postgres instance.
An incomplete bug report can lead to delays in resolving the issue or the closing of a ticket, so please be as detailed as possible.
If you are looking for general support, please view the support page for where you can ask questions.
Thanks for reporting the issue, we're looking forward to helping you!
Overview
I created a cluster called pgo-postgres-postgres-pg-vector. When Operator try to create the pgbackrest cronjob this create with a name of 54 chars of length and the k8s limit is 52.
Environment
Please provide the following details:
- Platform: (
Kubernetes) - Platform Version: (
1.19.15) - PGO Image Tag: (e.g.
ubi8-5.0.5-0) - Postgres Version (e.g.
14) - Storage: (
s3,nfs)
Steps to Reproduce
Create a postgrest cluster with a long name
Logs
time="2022-04-26T08:53:07Z" level=error msg="unable to reconcile Incremental backup for repo1" error="CronJob.batch \"pgo-postgres-postgres-pg-vector-pgbackrest-repo1-incr\" is invalid: metadata.name: Invalid value: \"pgo-postgres-postgres-pg-vector-pgbackrest-repo1-incr\": must be no more than 52 characters" file="internal/controller/postgrescluster/pgbackrest.go:2791" func="postgrescluster.(*Reconciler).reconcileScheduledBackups" name=pgo-postgres-postgres-pg-vector namespace=vector-search reconcileResource=repoCronJob reconciler group=postgres-operator.crunchydata.com reconciler kind=PostgresCluster version=5.0.5-0
Additional Information
Please provide any additional information that may be helpful.