Goal Summary:

 
ACS should have controls to to exclude CronJobs, Jobs and initContainers from liveness/readiness probe policies.

Goals and expected user outcomes:
 
When user creates a policy which flags as violation if a deployments does not have livenessProbe/readinessProbe, the policy also flags Jobs and CronJobs (which almost always do not have livenessProbe and/or readinessProbe) for violations.

Jobs/CronJobs are designed to complete and terminate successfully. Jobs and CronJobs have policies in their spec that specify how to handle successes or failures, livenessProbe is not required. Jobs/CronJobs do not run forever, so they almost always do not serve requests, so readinessProbe is not required.

Users should have options to exclude Jobs and CronJobs from livenessProbe/readinessProbe policy enforcement.

The same option, if implemented, should be made available to initContainers as well.

Acceptance Criteria:

  * user can (optionally) exclude Jobs and CronJobs (and initContainers) from livenessProbe/readinessProbe policy enforcement.

• livenessProbe/readinessProbe policy with exception for Jobs/CronJobs should not flag Jobs/CronJobs without livenessProbe/readinessProbe as violations.

Success Criteria or KPIs measured:

N/A

Use Cases (Optional):

N/A

Out of Scope (Optional):

N?A