Skip to content

Update readme - VPA-Autopilot vs. Kubernetes Native 1.34+ Features #41

@guillaumehospital-bib

Description

@guillaumehospital-bib

Description / update proposal:

Since Kubernetes 1.34 introduced more refined "Autopilot" signals, our feature effectively acts as the "Enforcer" that bridges the gap between the Recommender and the actual Deployment spec.

Currently, VPA-Autopilot excels at automatically creating VPA objects for Deployments to ensure they have right-sized recommendations. However, these values are not always enforced back onto the original Deployment manifests.

In Kubernetes 1.34+, while there are native mechanisms for VPA-Autopilot signals, there remains a gap in ensuring that the actual Deployment configuration is updated/enforced to match these recommendations. We have developed a feature that addresses this by allowing the controller to actively enforce/write back the recommended values to the Deployment.

If you are fine with that, I can propose PR to update the readme.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions