how to mount istio logs to efs

[ravi-rapyder]

Is there any way i can mount my istio access logs to efs - Lret me know

I have enabled access logs by following official documentation and now to mount it to efs how it is possible as you know

/dev/stdout is an special file system and cannot mount it directly and regarding other files we are getting permission denied error read only file system error is there any way that we can do this ?

/triage support

[k8s-ci-robot]

@ravi-rapyder: The label(s) triage/support cannot be applied, because the repository doesn't have them.

In response to this:

Is there any way i can mount my istio access logs to efs - Lret me know

I have enabled access logs by following official documentation and now to mount it to efs how it is possible as you know

/dev/stdout is an special file system and cannot mount it directly and regarding other files we are getting permission denied error read only file system error is there any way that we can do this ?

/triage support

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.

[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