[BUG] kb cluster sidecar containers have issues if has ResourceQuota API settings

[nashtsai]

Describe the bug
kb cluster sidecar containers have issues if has ResourceQuota API settings.

To Reproduce

apiVersion: v1
kind: ResourceQuota
metadata:
  name: quota
spec:
  hard:
    limits.cpu: "16"
    limits.ephemeral-storage: 100Gi
    limits.memory: 64Gi
    requests.storage: 100Gi

Expected behavior
(TBD, personally I would expect cluster controller detect the installing cluster NS reside ResourceQuota object, and has no LimitRange specifying default limits should report a "Warning" event with message that provides help to check appropriate-ness of ResourceQuota and LimitRange settings.)

Screenshots

[nashtsai]

@fireworm2002 @nayutah we need to discuss expect behavior.

[nashtsai]

ResourceQuota API should use with LimitRange API with default container settings.

apiVersion: v1
kind: LimitRange
metadata:
  name: range-{{ .Release.Namespace }}
  namespace: {{ .Release.Namespace }}
spec:
  limits:
  - default: # this section defines default limits
      cpu: 50m
      memory: 64Mi
    type: Container

[nashtsai]

@fireworm2002 @nayutah do check this bug's expect.

[nashtsai]