Add generic post upgrade hooks for node

[j4m3s-s]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

We have a couple of software systems which need to have actions correlated during kubernetes upgrade. Having hooks to do that would help us
Which issue(s) this PR fixes:

Special notes for your reviewer:

I am unsure if it would be better to add a default in the inventory group_vars instead with an appropriate comment ?

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @j4m3s-s. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[j4m3s-s]

I think all the CI errors are unrelated since my change doesn't change the default behaviour. Please correct me if it isn't.

[MrFreezeex]

/ok-to-test

[mzaian]

I think all the CI errors are unrelated since my change doesn't change the default behaviour. Please correct me if it isn't.

Thanks a lot @j4m3s-s

The CI part is fine now. Could you please add a proper release note.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: j4m3s-s, mzaian

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 [mzaian]

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

[yankay]

/lgtm