Skip to content
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
    • Kong Konnect
    • Kong Mesh
    • Plugin Hub
    • decK
    • Kubernetes Ingress Controller
    • Insomnia
    • Kuma

    • Docs contribution guidelines
  • Plugin Hub
  • Support
  • Community
  • Kong Academy
Early Access
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kubernetes Ingress Controller
  • Insomnia
  • Kuma

  • Docs contribution guidelines
    • Overview of Konnect
    • Architecture
    • Network Resiliency and Availability
    • Port and Network Requirements
    • Compatibility
    • Stages of Software Availability
    • Release Notes
      • Control Plane Upgrades FAQ
      • Supported Installation Options
    • Overview
    • Access a Konnect Account
    • Set up a Runtime
    • Configure a Service
    • Implement and Test the Service
      • Publish and Consume Services
      • Register Applications
    • Import Kong Gateway Entities into Konnect
    • Overview
      • Overview
      • Dashboard
      • Manage Runtime Groups with UI
      • Manage Runtime Groups with decK
      • Installation Options
      • Install with Docker
      • Install on Kubernetes
      • Install on Linux
      • Install on AWS
      • Install on Azure
      • Upgrade a Runtime Instance to a New Version
      • Renew Certificates
      • Runtime Parameter Reference
      • Overview
      • Runtime Configuration
    • Create Consumer Groups
      • Overview
      • Set Up and Use a Vault in Konnect
    • Plugin Ordering Reference
    • Troubleshoot
    • Overview
      • Konnect Services
      • Service Versions
      • Service Implementations
      • Manage Service Documentation
      • Overview
      • Configure a Plugin on a Service
      • Configure a Plugin on a Route
    • Overview
    • Access the Dev Portal
    • Sign Up for a Dev Portal Account
      • Manage Developer Access
      • Manage Application Registration Requests
      • Manage Application Connections
      • Auto Approve Dev and App Registrations
      • Azure OIDC
      • Application Overview
      • Enable and Disable App Registration
        • Okta
        • Curity
        • Auth0
      • Create, Edit, and Delete an Application
      • Register an Application with a Service
      • Generate Credentials for an Application
    • Customize Dev Portal
    • Troubleshoot
    • Introduction to Analytics
    • Summary Dashboard
    • Analyze Services and Routes
    • Generate Reports
    • Troubleshoot
      • Manage a Konnect Account or Plan
      • Change to a Different Plan
      • Manage Payment Methods and Invoices
      • Overview
        • Overview
        • Manage Teams
        • Teams Reference
        • Roles Reference
      • Manage Users
      • Set up SSO with OIDC
      • Set up SSO with Okta
    • Account and Org Deactivation
    • Troubleshoot
    • Overview
      • API Documentation
      • Identity Integration Guide
      • API Documentation
      • Overview
      • Nodes
      • Data Plane Certificiates
        • Services
        • Routes
        • Consumers
        • Plugins
        • Upstreams
        • Certificates
        • CA Certificates
        • SNIs
        • Targets
        • Vaults
      • API Spec
      • Filtering

github-edit-pageEdit this page

report-issueReport an issue

enterprise-switcher-iconSwitch to OSS

On this page
  • Are Konnect control plane and associated database migrations or upgrades done by Kong Inc?
  • Will Konnect control plane upgrades always show incompatible messages on the runtime manager page if the data planes are not the same version as the Konnect control plane?
  • Will new features be available if Konnect control plane detects incompatible data planes?
  • Can customers continue to use older versions of configurations as the Konnect control plane auto-upgrades?
  • Are there any disruptions if customers choose not to upgrade their data planes?
Kong Konnect
  • Home
  • Kong Konnect
  • Frequently Asked Questions - Control Plane Upgrades

Frequently Asked Questions - Control Plane Upgrades

Are Konnect control plane and associated database migrations or upgrades done by Kong Inc?

The Kong Gateway control plane and its dependencies are fully managed by Konnect. As new versions of Kong Gateway are released, Konnect supports them as long as they are under our active support schedule.

Will Konnect control plane upgrades always show incompatible messages on the runtime manager page if the data planes are not the same version as the Konnect control plane?

An old configuration may still be 100% compatible with older data planes and therefore not show any error messages in the Konnect UI. If there are compatibility issues detected when pushing the payload down to the data plane then this will be reflected in the UI.

Will new features be available if Konnect control plane detects incompatible data planes?

New features will not be available for use or consumption on incompatible data planes. You will see new features available in the Konnect UI regardless of the data plane that is connected to the control plane in Konnect. However, when an update payload is pushed to an incompatible data plane, the update will be automatically rejected by the data plane.

This is managed by a version compatibility layer that checks the payload before the update gets sent to the data plane. If there are concerns with the payload, metadata is added to the node. That metadata is what will display incompatibility warnings or errors in the Konnect UI.

For example, let’s say a parameter is introduced with a new version of a plugin, and is available in the Konnect UI. The data plane, however, is running an older version of Kong Gateway and doesn’t support the new parameter. If that parameter is not configured, or is assigned the default value, then no warning or incompatibility metadata will be applied to the node in Konnect, and no warnings or errors will appear.

Can customers continue to use older versions of configurations as the Konnect control plane auto-upgrades?

Yes all decK dumps, or YAML configurations, will continue to work in Konnect after they are synced.

Are there any disruptions if customers choose not to upgrade their data planes?

There is NO disruption at all if customers choose NOT to upgrade their data planes, as long as the version of the data plane is under our Kong Gateway active support timeline.

Thank you for your feedback.
Was this page useful?
  • Kong
    THE CLOUD CONNECTIVITY COMPANY

    Kong powers reliable digital connections across APIs, hybrid and multi-cloud environments.

    • Company
    • Customers
    • Events
    • Investors
    • Careers Hiring!
    • Partners
    • Press
    • Contact
  • Products
    • Kong Konnect
    • Kong Gateway
    • Kong Mesh
    • Get Started
    • Pricing
  • Resources
    • eBooks
    • Webinars
    • Briefs
    • Blog
    • API Gateway
    • Microservices
  • Open Source
    • Install Kong Gateway
    • Kong Community
    • Kubernetes Ingress
    • Kuma
    • Insomnia
  • Solutions
    • Decentralize
    • Secure & Govern
    • Create a Dev Platform
    • API Gateway
    • Kubernetes
    • Service Mesh
Star
  • Terms•Privacy
© Kong Inc. 2023