Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/Influxdb] RetentionDays parameter does not work on AWS S3 Storage #31084

Open
syakirali opened this issue Dec 18, 2024 · 1 comment · May be fixed by #31087
Open

[bitnami/Influxdb] RetentionDays parameter does not work on AWS S3 Storage #31084

syakirali opened this issue Dec 18, 2024 · 1 comment · May be fixed by #31087
Assignees
Labels
influxdb tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@syakirali
Copy link

syakirali commented Dec 18, 2024

Name and Version

bitnami/influxdb 6.5.0

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Install influxdb chart with the backup option enabled and set uploadProviders to aws

Are you using any custom parameters or values?

backup:
  enabled: true
  retentionDays: 1
  cronjob:
    schedule: "0 0 * * *"

  uploadProviders:
    aws:
      enabled: true
      accessKeyID: "secret"
      secretAccessKey: "secret"
      bucketName: "s3://influxdb"
      endpoint: "http://s3url"

persistence:
  enabled: true
  size: 15Gi

What is the expected behavior?

The old backup in AWS S3 storage was also deleted after the aws sync command.

What do you see instead?

The old backup in AWS S3 storage still exists.

@syakirali syakirali added the tech-issues The user has a technical issue about an application label Dec 18, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 18, 2024
@syakirali syakirali changed the title Influxdb's retentionDays parameter does not work on AWS S3 Storage [bitnami/Influxdb] RetentionDays parameter does not work on AWS S3 Storage Dec 18, 2024
@syakirali syakirali linked a pull request Dec 18, 2024 that will close this issue
4 tasks
@carrodher
Copy link
Member

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
influxdb tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants