Upgrade Insights

Cloud Providers sometimes provide their own Kubernetes upgrade intelligence which Plural can directly integrate with, and in addition, especially with EKS, they have their own add-on ecosystem that users need to be aware of at Kubernetes upgrade-time. The Plural operator can scrape these endpoints and aggregate them centrally in our API for single-pane-of-glass visibility, this provides a few key benefits:

• Unified dashboard to understand kubernetes upgrade-relevant information (no switching between AWS accounts and regions)
• Aggregating that information alongside Plural's own upgrade intelligence to get a holistic upgradeability picture
• Unified understanding of what EKS Add-Ons are present and whether they are latent risks for a future upgrade

Supported providers

Currently, the following provider is supported:

• Amazon Elastic Kubernetes Service (EKS)

Configuration

Upgrade Insights can be configured using our Custom Resource Definition (CRD). This configuration allows you to provide custom credentials, which are used to access the cloud provider's API and gather relevant information. For the EKS provider, we automatically configure node-level permissions during the cluster bootstrapping process with Plural, enabling our operator to retrieve upgrade insights.

Relying on Node-Level Permissions

Alternatively, you can rely on node-level permissions via the cloud provider's assume role feature with the following configuration:

apiVersion: deployments.plural.sh/v1alpha1
kind: UpgradeInsights
metadata:
  name: eks-upgrade-insights
spec:
  distro: EKS
  clusterName: "<CLUSTER_NAME>"
  interval: 10m