Bug 1933666: [release-4.6] Create ImageStream and other resources for samples step by step

[jerolimov]

This is a manual cherry-pick of #8222 because DevFile changes are not available in 4.6

BZ for 4.6 https://bugzilla.redhat.com/show_bug.cgi?id=1933666 depends on 4.7 https://bugzilla.redhat.com/show_bug.cgi?id=1933665 which depends on 4.8 issue https://bugzilla.redhat.com/show_bug.cgi?id=1933664

edit: This also fixes https://bugzilla.redhat.com/show_bug.cgi?id=1921717 (Deployment creates a huge number of ReplicaSets)

/assign jerolimov

[openshift-ci-robot]

@jerolimov: This pull request references Bugzilla bug 1933666, which is invalid:

• expected dependent Bugzilla bug 1933665 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1933666: [release-4.6] Create ImageStream and other resources for samples step by step

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.

[jerolimov]

/kind bug

[jerolimov]

Tested this branch locally with a 4.6 cluster.

/lgtm

[openshift-ci-robot]

@jerolimov: you cannot LGTM your own PR.

In response to this:

Tested this branch locally with a 4.6 cluster, works for me.

/lgtm

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.

[jerolimov]

/bugzilla refresh

[openshift-ci-robot]

@jerolimov: This pull request references Bugzilla bug 1933666, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.z) matches configured target release for branch (4.6.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1933665 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1933665 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gamore@redhat.com), skipping review request.

In response to this:

/bugzilla refresh

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-ci-robot]

@jerolimov: This pull request references Bugzilla bug 1933666, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.z) matches configured target release for branch (4.6.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1933665 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1933665 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gamore@redhat.com), skipping review request.

In response to this:

Bug 1933666: [release-4.6] Create ImageStream and other resources for samples step by step

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-ci-robot]

@jerolimov: This pull request references Bugzilla bug 1933666, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.z) matches configured target release for branch (4.6.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1933665 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1933665 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gamore@redhat.com), skipping review request.

In response to this:

Bug 1933666: [release-4.6] Create ImageStream and other resources for samples step by step

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.

[jerolimov]

/assign @christianvogt

[jerolimov]

Checked this now on a cluster-bot cluster for this PR as well. With this PR the resources are created sequential instead of parallel. Here is the recorded network tab in Chrome:

Peek.2021-04-07.10-56.mp4

/lgtm

[openshift-ci-robot]

@jerolimov: you cannot LGTM your own PR.

In response to this:

Checked this now on a cluster-bot cluster for this PR as well. With this PR the resources are created sequential instead of parallel. Here is the recorded network tab in Chrome:

Peek.2021-04-07.10-56.mp4

/lgtm

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.

[christianvogt]

/lgtm
/approve

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christianvogt, jerolimov

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:

• frontend/packages/dev-console/OWNERS [christianvogt]

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

[mfojtik]

[patch-manager] ⌛ This pull request was not picked by the patch manager for the current z-stream window and have to wait for the next window.

• Score: 0.10
• Reason: maximum total for this z-stream is 10

NOTE: This message was automatically generated, if you have questions please ask on #forum-release

[jerolimov]

/bugzilla refresh

[openshift-ci-robot]

@jerolimov: This pull request references Bugzilla bug 1933666, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.z) matches configured target release for branch (4.6.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
• dependent bug Bugzilla bug 1933665 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
• dependent Bugzilla bug 1933665 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gamore@redhat.com), skipping review request.

In response to this:

/bugzilla refresh

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-ci-robot]

@jerolimov: All pull requests linked via external trackers have merged:

• openshift/console#8261

Bugzilla bug 1933666 has been moved to the MODIFIED state.

In response to this:

Bug 1933666: [release-4.6] Create ImageStream and other resources for samples step by step

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.