Skip to main content

Apply whitelist on EKS Public endpoint and enable private endpoints

Feature Request

We will allow you to set a CIDR whitelist on the public endpoints of your managed EKS cluster. This is mostly required for compliance reasons.

We will also enable the private endpoint of your EKS cluster.

Posted by Alessandro Carrano ·
Status: ✅ Done1 comment

Log in to comment and vote

Comments1

  • Alessandro Carrano

    Team•

    Oct 11, 2024

    The feature has been delivered! Note: it is available only for AWS clusters

    We strongly recommend you to test it on your non-production cluster before moving to the production one.

    how to activate it:

    • ensure to have a [Dockerhub registry] created and configured with your own credentials. As explained above, this is a requirement we have set to avoid rate limit issues when pulling images from the Dockerhub registry (more info here).

    • set the cluster advanced settings qovery.static_ip_mode to true

    • re-deploy your cluster

    This will apply a whitelist on the cluster public endpoints and activate the private endpoint.

    if you need access to the Kube API from other locations (like connecting via k9s from your own laptop), you will have to add those additional IP/CIDR in the advanced settings k8s.api.allowed_public_access_cidrs

    Update: we have been giving access for free to this feature to our existing customers but given the infrastructure cost and the value it brings from a security stand-point we will add it to our pricing page in a dedicated section.

    Let me know if you need more information