You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with/fresh will mark this issue as not stale.
This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!
What problem are you facing?
I am experimenting to run upbound provider in regulated industry , As it has mandate requirement to enable liveness/readiness probe for all pods
I checked with Controller config seems can set podSecurityContext and securityContext but doesn't have mechanism to create probes .
How could Official AWS Provider help solve your problem?
I am not sure how lifecyle of the pod is maintained
The text was updated successfully, but these errors were encountered: