feat(vpa-chart): add chart logic for the vpa recommender

[maxcao13]

Which issue(s) this PR fixes:

Part of: #8587

Adds to the VPA helm chart:

For vpa-recommender:

• Deployment
• ServiceAccount
• RBAC (ClusterRole, RoleBinding)
• ConfigMap (optional tuning parameters)
• PodDisruptionBudget
• nodeSelector / affinity / tolerations

Updates chart version to 0.4.0.

What type of PR is this?

/kind feature

You can test it out by using this:

helm upgrade --install vpa ./vertical-pod-autoscaler/charts/vertical-pod-autoscaler/ \
  -n vpa --create-namespace \
  --set recommender.enabled=true \
  --set recommender.replicas=2 \
  --set recommender.image.tag=1.5.0 \
  --set recommender.image.pullPolicy=Always \
  --set-json 'recommender.podLabels={"environment":"test","team":"autoscaling"}' \
  --set-json 'recommender.podAnnotations={"prometheus.io/scrape":"true","prometheus.io/port":"8942"}' \
  --set-json 'recommender.serviceAccount.labels={"app":"vpa"}' \
  --set-json 'recommender.serviceAccount.annotations={"example.com/owner":"platform-team"}' \
  --set-json 'recommender.nodeSelector={"kubernetes.io/os":"linux"}' \
  --set-json 'recommender.tolerations=[{"key":"dedicated","operator":"Equal","value":"system","effect":"NoSchedule"}]' \
  --set-json 'recommender.affinity={"podAntiAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"weight":100,"podAffinityTerm":{"labelSelector":{"matchExpressions":[{"key":"app.kubernetes.io/component","operator":"In","values":["recommender"]}]},"topologyKey":"kubernetes.io/hostname"}}]}}' \
  --set recommender.resources.limits.cpu=500m \
  --set recommender.resources.limits.memory=2Gi \
  --set recommender.resources.requests.cpu=100m \
  --set recommender.resources.requests.memory=512Mi \
  --set-json 'recommender.extraArgs=["--v=5","--pod-recommendation-min-cpu-millicores=15","--pod-recommendation-min-memory-mb=100","--leader-elect=true","--leader-elect-resource-namespace=vpa"]' \
  --set-json 'recommender.extraEnv=[{"name":"LOG_LEVEL","value":"debug"},{"name":"GOMAXPROCS","value":"4"}]' \
  --set recommender.podDisruptionBudget.enabled=true \
  --set recommender.podDisruptionBudget.minAvailable=1

Special notes for your reviewer:

I was mostly just following the existing manifests in veritcal-pod-autoscaler/deploy/*.yaml

Does this PR introduce a user-facing change?

[maxcao13]

/hold
because of #8617

I will also let #8642 merge first because it is changing chart release version.

[maxcao13]

/release-note-none

[adrianmoisey]

I believe you are unblocked now

[maxcao13]

Sorry, I was on holiday 😅 , I can rebase today.

[maxcao13]

/unhold

[omerap12]

Overall lgtm

[omerap12]

I tested it using the default setup:
helm upgrade --install vpa ./vertical-pod-autoscaler/charts/vertical-pod-autoscaler/ -n vpa --create-namespace
Since this is the typical way users would install it, it makes sense to test it that way. looks good to me.

[omerap12]

Thanks Max!
/lgtm
/assign @adrianmoisey

[adrianmoisey]

/approve

thank you!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianmoisey, maxcao13

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• vertical-pod-autoscaler/charts/vertical-pod-autoscaler/OWNERS [adrianmoisey]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment