Bug 1897423: Update dc strategy type and rolling params

[yapei]

Deployment Config Details page is not showing Max unavailable and Max surge
Fixed it to use correct strategy type and parse from correct path
@jhadvig Could you help review?

[openshift-ci-robot]

@yapei: This pull request references Bugzilla bug 1897423, which is invalid:

• expected the bug to target the "4.7.0" release, but it targets "---" 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 1897423: Update dc strategy type and rolling params

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]

@yapei: This pull request references Bugzilla bug 1897423, which is invalid:

• expected the bug to target the "4.7.0" release, but it targets "---" 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:

/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.

[yapei]

/bugzilla refresh

[openshift-ci-robot]

@yapei: This pull request references Bugzilla bug 1897423, 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.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.0) matches configured target release for branch (4.7.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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.

[yapei]

/test e2e-gcp-console

[openshift-ci-robot]

@yapei: This pull request references Bugzilla bug 1897423, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.7.0) matches configured target release for branch (4.7.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1897423: Update dc strategy type and rolling params

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.

[spadgett]

/lgtm

[spadgett]

/cherry-pick release-4.6

[openshift-cherrypick-robot]

@spadgett: once the present PR merges, I will cherry-pick it on top of release-4.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.6

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spadgett, yapei

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/OWNERS [spadgett]

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

[openshift-ci-robot]

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

• openshift/console#7200

Bugzilla bug 1897423 has been moved to the MODIFIED state.

In response to this:

Bug 1897423: Update dc strategy type and rolling params

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

@spadgett: #7200 failed to apply on top of branch "release-4.6":

Applying: Bug 1897423: Update dc strategy type and rolling params
Using index info to reconstruct a base tree...
M	frontend/public/components/deployment-config.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/deployment-config.tsx
CONFLICT (content): Merge conflict in frontend/public/components/deployment-config.tsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bug 1897423: Update dc strategy type and rolling params
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.6

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.

[yapei]

/cherry-pick release-4.6

[openshift-cherrypick-robot]

@yapei: #7200 failed to apply on top of branch "release-4.6":

Applying: Bug 1897423: Update dc strategy type and rolling params
Using index info to reconstruct a base tree...
M	frontend/public/components/deployment-config.tsx
Falling back to patching base and 3-way merge...
Auto-merging frontend/public/components/deployment-config.tsx
CONFLICT (content): Merge conflict in frontend/public/components/deployment-config.tsx
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bug 1897423: Update dc strategy type and rolling params
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.6

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.