operator YAML including the status field

[rienafairefr]

The fluent-bit operator setup YAML (the version I got, at https://raw.githubusercontent.com/kubesphere/fluentbit-operator/release-0.8/manifests/setup/setup.yaml) includes the status field in the resources:

status:
  acceptedNames:
    kind: ""
    plural: ""
  conditions: []
  storedVersions: []

AFAIK, this is not needed because the status will be set by the kube apiserver ?

With 'normal' kubectl apply it doesn't really matter, I think, but in some cases it might (I saw a problem when deploying through terraform kubernetes_manifest for example)

[wenchajun]

This is automatically generated. We use KubeBuilder to develop fluentBit-Operator.For details, please refer to https://book-v1.book.kubebuilder.io/basics/status_subresource.html. CRD generation tool will use the +kubebuilder:subresource:status annotation to enable status subresource in the CRD definition. So, if you run make manifests , it will regenerate the CRD manifests under config/crds/<kind_types.yaml.