sail-operator CRDs

[JustAnotherITPerson]

Migrating from istio-operator to the sail-operator which we deploy using Kustomize (deployed through ArgoCD) and I've found that the sail-operator CRDs (istiorevisions.sailoperator.io and istios.sailoperator.io) are enormous (600kb+). This goes through a kubectl apply hence the error message:

make deploy Using known safe context, proceeding... kubectl create namespace sail-operator --dry-run=client -o yaml | kubectl apply -f - namespace/sail-operator configured kustomize build . --enable-alpha-plugins | kubectl apply -f - customresourcedefinition.apiextensions.k8s.io/authorizationpolicies.security.istio.io created customresourcedefinition.apiextensions.k8s.io/destinationrules.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/envoyfilters.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/gateways.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/istiocnis.sailoperator.io created customresourcedefinition.apiextensions.k8s.io/istiorevisiontags.sailoperator.io created customresourcedefinition.apiextensions.k8s.io/peerauthentications.security.istio.io created customresourcedefinition.apiextensions.k8s.io/proxyconfigs.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/requestauthentications.security.istio.io created customresourcedefinition.apiextensions.k8s.io/serviceentries.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/sidecars.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/telemetries.telemetry.istio.io created customresourcedefinition.apiextensions.k8s.io/virtualservices.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/wasmplugins.extensions.istio.io created customresourcedefinition.apiextensions.k8s.io/workloadentries.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/workloadgroups.networking.istio.io created customresourcedefinition.apiextensions.k8s.io/ztunnels.sailoperator.io created serviceaccount/sail-operator created role.rbac.authorization.k8s.io/leader-election-role created clusterrole.rbac.authorization.k8s.io/metrics-reader created clusterrole.rbac.authorization.k8s.io/sailoperator-proxy-role created clusterrole.rbac.authorization.k8s.io/sailoperator-role created rolebinding.rbac.authorization.k8s.io/leader-election-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/sailoperator-proxy-rolebinding created clusterrolebinding.rbac.authorization.k8s.io/sailoperator-rolebinding created service/sail-operator-metrics-service created deployment.apps/sail-operator created Error from server (Invalid): error when creating "STDIN": CustomResourceDefinition.apiextensions.k8s.io "istiorevisions.sailoperator.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes Error from server (Invalid): error when creating "STDIN": CustomResourceDefinition.apiextensions.k8s.io "istios.sailoperator.io" is invalid: metadata.annotations: Too long: must have at most 262144 bytes make: *** [deploy] Error 1

Outside of Kustomize the only other deployment option I have is a pipeline that does a helm template and kubectl apply. I've been trying to write something that would remove the description text at least to try and shrink this file but wondering if there is another option here or if you would consider a chart option to reduce CRD size but excluding descriptions?

[fjglira]

Hi @JustAnotherITPerson, regarding this, we can try to provide a strip without all the validations and descriptions, but also you can write a simple script that parses using yq the yaml files in the folder and removes all the descriptions in some automatic way

[JustAnotherITPerson]

Yes I had to write a script to strip the descriptions but would be useful as a helm value or something