@navneet066 Thanks for the PR, the resources in values are for the fluentbit daemonset.
The resources for FluentBit Operator itself needn't to be configurable

I see. I think we should have the flexibility to modify resources for the operator also. If you are agreeing to this, we can add the resources section for fluentbit-operator deployment in values.yaml file. Please let me know your thoughts.

The resources consumed by the operator usually keep consistent actually, so it's ok to use default values for that.
Of course you can also add them to values.

The values could be adjust like below:

fluentbit:
  # Fluent Bit resources. User can adjust it based on the log volume.
  resources:
     limits:
       cpu: 500m
       memory: 200Mi
     requests:
       cpu: 10m
       memory: 25Mi

operator:
  # FluentBit operator resources. Usually user needn't to adjust these.
  resources:
    limits:
      cpu: 200m
      memory: 50Mi
  requests:
    cpu: 100m
    memory: 20Mi

Yes. Usually, it is really low. But when the number of nodes in the K8S is high, say 100 or so, It may generate more pressure on the fluentbit-operator. Thanks for the snippet. Shall I add this to the file and update the PR?

Yes. Usually, it is really low. But when the number of nodes in the K8S is high, say 100 or so, It may generate more pressure on the fluentbit-operator. Thanks for the snippet. Shall I add this to the file and update the PR?

the fluentbit-operator just needs to reconcile several crds like FluentBit FluentBitConfig Input parser filter and output no matter how many nodes there actually.

Yes, you can add this to values and update the PR

Made the corresponding changes @benjaminhuo . Please have a review and let me know if any other changes are required

@wanjunlei @wenchajun Please help to review this

Maybe you should check the format，such as resources (fluentbit-operator-deployment.yaml), fluentbit.resources.limit (values.yaml ). Please modify its format. Two spaces may be better.

Thank you for your suggestion @wenchajun . I updated the changes as per your comment.

Thanks a lot. But there's still something wrong here. You can learn more about the toyaml function. such as operator.requests (chart/fluentbit-operator/values.yaml). It is wrong.

@wenchajun I have made the changes as per the review. Sorry for the iterations. It should be fine now