WIP - Proposal on Image availability

[smarterclayton]

Covers how we can ensure failures of external registries do not impact overall application availability.

[smarterclayton]

@bparees @mfojtik @legionus @miminar @dmage some discussions started last week about how we can mitigate downtime of external registries (like registry.access.redhat.com), as well as optimize access to content. This contains some ideas that we've discussed in many other areas (access to public images, mirroring, promotion), but specifically focused around the question:

How do we guarantee maximum uptime of running applications in the face of external failures?

Please contribute back - i assume there's lots of things you guys have discussed that relate and I'd like to make this as comprehensive as possible.

[enj]

@openshift/sig-security

[openshift-ci-robot]

@smarterclayton: Your pull request title starts with "WIP", so the do-not-merge/work-in-progress label will be added.

This label will ensure that your pull request will not be merged. Remove the prefix from your pull request title to trigger the removal of the label and allow for your pull request to be merged.

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/test-infra repository.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[bparees]

@smarterclayton should this be turned into a trello card for follow up?

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• ~~OWNERS~~ [smarterclayton]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[bparees]

/remove-lifecycle rotten

/lifecycle frozen

[openshift-bot]

/test cross

[liggitt]

/unassign

[openshift-ci-robot]

@smarterclayton: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/openshift-jenkins/unit	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test unit
ci/prow/cross	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test cross
ci/prow/launch-aws	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test launch-aws
ci/prow/e2e-aws-serial	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test e2e-aws-serial
ci/prow/unit	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test unit
ci/prow/e2e-aws	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[openshift-merge-robot]

@smarterclayton: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-agnostic-cmd	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test e2e-agnostic-cmd

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

[openshift-ci[bot]]

@smarterclayton: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-jenkins	a11b7e70cb655b06ad3498a551821fecbc28ccca	link	/test e2e-aws-jenkins

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.