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

Configure liveness/readiness check for provider pods #865

Closed
shukla2009 opened this issue Sep 6, 2023 · 3 comments
Closed

Configure liveness/readiness check for provider pods #865

shukla2009 opened this issue Sep 6, 2023 · 3 comments
Labels

Comments

@shukla2009
Copy link

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

@shukla2009 shukla2009 added enhancement New feature or request needs:triage labels Sep 6, 2023
Copy link

github-actions bot commented Apr 2, 2024

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.

Copy link

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.

@github-actions github-actions bot added the stale label Aug 17, 2024
Copy link

github-actions bot commented Sep 3, 2024

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!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants