Can I use a sidecar as an init container?

[BryanDollery]

To rephrase the question: is it ok for my sidecar to exit?

I want to use all the features of the kruise sidecar capability to inject init containers. This will enable the init container without having to burden my engineers with specifying an init container in their deployment yaml files.

So, is there a problem with doing this?

I'm asking because I am having problems with my sidecar and I can't yet tell if it's something I've done or if kruise has a problem with my sidecar exiting early.

TIA

[FillZpp]

1. You can define initContainers in SidecarSet, so that it will inject the init containers when new pods created. Refer to this doc.
2. SidecarSet does not care of the existing sidecar or init containers in early pods.

(I'm not sure if I got all your questions)

[FillZpp]

@qixiaobo Good question. Are the init containers defined in a signal sidecarset or multiple sidecarsets?

[qixiaobo]

@qixiaobo Good question. Are the init containers defined in a signal sidecarset or multiple sidecarsets?

Maybe other team[even cloud provider] defined admission hooks.
You may have a look at arms or mse

[qixiaobo]

@qixiaobo Good question. Are the init containers defined in a signal sidecarset or multiple sidecarsets?

Maybe other team[even cloud provider] defined admission hooks. You may have a look at arms or mse

Arms url below
https://help.aliyun.com/document_detail/103108.html

[FillZpp]

kube-apiserver will sort all mutating webhooks by their names and calls them with the name order.

[qixiaobo]

kube-apiserver will sort all mutating webhooks by their names and calls them with the name order.

Yeah, for me . K8s make sure for different webhooks in alpha order. So the last order webhook may has chance to reorder all sidecars.