Setup the sidecar and main container start/shutdown sequence.

[ryanzhang-oss]

Describe the bug

The sidecar currently starts alongside the main container. We would like to make sure the main container does not start before the sidecar has dropped the credential to the bonded volume. In this way, we can clearly identify the problem.

Environment

Please provide the following:

• Hub cluster details
• Member cluster details

To Reproduce

Steps to reproduce the behavior:

Expected behavior

the main container does not start until the hub cluster credential is dropped in.

Additional context

https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/

[zhiying-lin]

https://medium.com/@marko.luksa/delaying-application-start-until-sidecar-is-ready-2ec2d21a7b74 useful doc to explain how post-start should be configured