Data repository integration s3 automatic sync

[ilkarataev]

Hi gyus, Thank you for you work. I see that Fsx Lustre now can do full bi-directional synchronization for s3. We need configure an automatic export policy for your data repository association, files on your FSx for Lustre file system are automatically exported to your data repository. In storage class we don't have this option. I see that in api aws 2. Have AutoExportPolicy and AutoImportPolicy https://github.com/aws/aws-sdk-go/blob/v1.44.96/service/fsx/api.go#L15954-L15964 https://docs.aws.amazon.com/sdk-for-go/api/service/fsx/#AutoImportPolicy Thank you and have a nice day.

[PatrickGhadban]

Hi, thank you for bringing this to our attention. I've created a ticket for us to add support for AutoExportPolicy to dynamic provisioning. In the meantime, it is possible to create a Lustre file system with AutoExportPolicy & AutoImportPolicy and use static provisioning then it could be mounted inside container as a volume using the Driver.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[jacobwolfaws]

/kind feature /remove-lifecycle rotten

[elgalu]

/kind feature /remove-lifecycle rotten

[jacobwolfaws]

/lifecycle frozen