Skip to content
2023 API Summit Hackathon: Experiment with AI for APIs (August 28 - September 27) Learn More →
Kong Logo | Kong Docs Logo
search
  • We're Hiring!
  • Docs
    • Kong Gateway
      Lightweight, fast, and flexible cloud-native API gateway
      Kong Konnect
      Single platform for SaaS end-to-end connectivity
      Kong Mesh
      Enterprise service mesh based on Kuma and Envoy
      decK
      Helps manage Kong’s configuration in a declarative fashion
      Kong Ingress Controller
      Works inside a Kubernetes cluster and configures Kong to proxy traffic
      Kong Gateway Operator
      Manage your Kong deployments on Kubernetes using YAML Manifests
      Insomnia
      Collaborative API development platform
      Kuma
      Open-source distributed control plane with a bundled Envoy Proxy integration
  • API Specs
  • Plugin Hub
    • Explore the Plugin Hub
      View all plugins View all plugins View all plugins arrow image
    • Functionality View all View all arrow image
      View all plugins
      Authentication's icon
      Authentication
      Protect your services with an authentication layer
      Security's icon
      Security
      Protect your services with additional security layer
      Traffic Control's icon
      Traffic Control
      Manage, throttle and restrict inbound and outbound API traffic
      Serverless's icon
      Serverless
      Invoke serverless functions in combination with other plugins
      Analytics & Monitoring's icon
      Analytics & Monitoring
      Visualize, inspect and monitor APIs and microservices traffic
      Transformations's icon
      Transformations
      Transform request and responses on the fly on Kong
      Logging's icon
      Logging
      Log request and response data using the best transport for your infrastructure
  • Support
  • Community
  • Kong Academy
Get a Demo Start Free Trial
Kong Mesh
2.0.x
  • Home icon
  • Kong Mesh
  • Documentation
  • Upgrades
github-edit-pageEdit this page
report-issueReport an issue
  • Kong Gateway
  • Kong Konnect
  • Kong Mesh
  • Plugin Hub
  • decK
  • Kong Ingress Controller
  • Kong Gateway Operator
  • Insomnia
  • Kuma

  • Docs contribution guidelines
  • 2.4.x (latest)
  • 2.3.x
  • 2.2.x
  • 2.1.x
  • 2.0.x
  • 1.9.x
  • 1.8.x
  • 1.7.x
  • 1.6.x
  • 1.5.x
  • 1.4.x
  • 1.3.x
  • 1.2.x
enterprise-switcher-icon Switch to OSS
On this pageOn this page
  • Standalone
  • Multizone
You are browsing documentation for an outdated version. See the latest documentation here.

Upgrades

Since Kong Mesh 1.4.x upgrades can be performed up to two minor versions. Examples:

  • You can upgrade from 1.5.x to 1.6.x
  • You can upgrade from 1.4.x to 1.6.x
  • To upgrade from 1.2.x to 1.6.x, first upgrade from 1.2.x to 1.4.x. Then from 1.4.x to 1.6.x.

To avoid control plane downtime when restarting on the new version make sure you have more than one instance of the control plane in each zone.

kuma-dp follows the above compatibility rules with kuma-cp. Examples:

  • You can connect kuma-dp 1.4.x to kuma-cp 1.6.x
  • You cannot connect kuma-dp 1.3.x to kuma-cp 1.6.x. It may cause undefined behavior.

Global control plane follows the above compatibility rules with zone control planes. Examples:

  • You can connect zone control plane 1.4.x to global control plane 1.6.x.
  • You cannot connect zone control plane 1.3.x to global control plane 1.6.x. It may cause undefined behavior.

Despite control-planes within a zone not connecting to each other; they share a common store (usually Kubernetes or Postgres), compatibility of the storage layer follows the above rules too:

  • You can read any data written with a control-plane 1.4.x with a control-plane version 1.6.x.
  • You can read any data written with a control-plane 1.6.x with a control-plane version 1.4.x.
  • You cannot read data written with a control-plane 1.3.x with a control-plane version 1.6.x or higher. It may cause undefined behavior.
  • You cannot read data written with a control-plane 1.6.x with a control-plane version 1.3.x or lower. It may cause undefined behavior.

Some feature flags may not provide backward compatibility, when this is the case it is clearly documented in the control-plane configuration and will be part of the experimental section.

To guarantee our compatibility policy we will always wait at least two minor versions before making these features enabled by default.

Standalone

To upgrade Kong Mesh with a standalone deployment, first upgrade the control plane, then upgrade data plane proxies. To upgrade data plane proxies on Kubernetes, rollout the new deployment. This way injector will inject the newest sidecar.

Multizone

To upgrade Kong Mesh with a multizone deployment, first upgrade the global control plane. Then, upgrade zone control planes. As a last step, upgrade data plane proxies.

Thank you for your feedback.
Was this page useful?
Too much on your plate? close cta icon
More features, less infrastructure with Kong Konnect. 1M requests per month for free.
Try it for Free
  • 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