🚀 Feature Description and Motivation

Follow up #793.

Previously, we use apply --server-side as a temporary solution but field ownership mechanism will check field owner, if user mix use different way to upgrade the service, for example, kubectl edit or kubectl apply, it will result in conflicts. That's why some crds was moved to dependencies folder in #793, but this is not something very elegant,

• We should separate CRDs from components deployments
• dependency is a logical concepts, it mainly focus on non-aibrix namespace system dependencies like envoy-gateway etc.

Use Case

for easy installation and upgrade

Proposed Solution

• Separate CRDs from current manifest and install it separately. this is a common practice