registry_pod: Avoid grace period delay

[avisiedo]

Description of the change:

Substitute shell by the last command that serve the registry pod.

Motivation for the change:

The shell script does not propagate the SIGTERM signal that is sent to the pod when it is terminated; to avoid this, we run the last command to substitute the shell process, so that the pod stop immediately instead of waiting the 30 default seconds of the grace period when an user uninstall the operator by using 'operator-sdk cleanup ...' command.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

• [ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
• [ ] Add or update relevant sections of the docs website in website/content/en/docs

issue: https://github.com/operator-framework/operator-sdk/issues/5866

[jmrodri]

@avisiedo is there a github issue that explains the problem you were having?

[avisiedo]

@jmrodri No, there is not. What am I missing to propose a change into the repository?

• I don't see the change as a user-facing change, as the operations and interactions are the same, just improve the time the registry_pod to terminate. Should documentation about this to be provided for the changeling anyway?
• The same for 'website/content/en/docs', as I don't see changes into the user interaction with this change.

Please correct me on the above if I were wrong in something, and if an issue is required, let me know and I will create it, and I will update this PR to reference the issue.

Thanks

[avisiedo]

/retest

[openshift-ci[bot]]

@avisiedo: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[avisiedo]

@jmrodri In the pipeline I get here and issue related with an external link.

I have checked the link manually and it worked, probably network transitory situations; I can not relaunch the test to check it. :sweat_smile:

If further changes are necessary, or an issue ticket is necessary for the change, please let me know and I will do it

Cheers! :slightly_smiling_face:

[avisiedo]

I have added an issue at: https://github.com/operator-framework/operator-sdk/issues/5866

[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

[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

[openshift-ci[bot]]

@openshift-bot: Closed this PR.

In response to this:

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

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.