Skip to content
Kong Logo | Kong Docs Logo
search
  • Docs
    • Explore the API Specs
      View all API Specs View all API Specs View all API Specs arrow image
    • Documentation
      API Specs
      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
  • 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 Konnect
  • Home icon
  • Kong Konnect
  • Gateway Manager
  • Control Plane Groups
  • Conflicts in control planes
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
enterprise-switcher-icon Switch to OSS

Conflicts in control planes

When combining configuration from individual control planes into a control plane group, you might run into conflicts. For example, there might be a name conflict between services, or the existence of consumer credentials, which become available to all members of a control plane group.

Once you have at least one data plane node connected to your control plane group, you may see one of the following error messages:

Control plane group:

Conflicts have been detected between these control planes: 
<control plane name>
<control plane name>

Standard control plane:

This control plane is causing a conflict with the parent control plane group.

You can follow the link from the notification to View the conflicts in each control plane, then View again to open the resource that’s causing the issue.

The control plane won’t send any config updates to its data plane nodes until conflicts are resolved.

See the following table for a breakdown of potential issues, their causes, and recommended solutions:

Conflict Description Action
Duplicate names across control plane group members Entity names within a standard control plane must be unique. However, it’s possible to create entities with the same name in different standard control planes. When those control plane are added as members of the same control plane group, the control plane group ends up having entities with duplicate names. The duplicate entities behave as regular entities in the data plane. Resolve the conflict by removing or renaming one of the instances.
Shared credentials across control plane group members Consumer credentials in one control plane group member can be used to authenticate to everything registered in the group. If you don’t want to share credentials across the members, identify and remove those credentials.
ACL group names across control plane group members ACL groups names can be referenced across control plane group members for authorization. If you don’t want to share ACL groups across the members, identify and remove duplicates.
Consumer groups across control plane group members Consumer group names in the Rate Limiting Advanced plugin can reference group names from other control plane group members. If you don’t want to share consumer groups across the members, identify and remove duplicates.
decK dump with duplicate names found deck dump will break with duplicate names across control plane group entities. Resolve the conflict by removing or renaming one of the instances.
Reference by name vs reference by ID If the entity relationship requires reference by ID, then relationships across control planes don’t work. If the entity relationship is defined by a special string, relationships across control planes do work as long as you know the string. Resolve the conflict by removing one of the instances.
Multiple instances of the same global plugin A global plugin can only be applied once in an standard control plane. However, multiple instances of the same global plugin can be combined into the control plane group. Resolve the conflict by removing one of the instances, or setting different instance names for the plugins.

Note: If you want to limit which users can apply global plugins, add all global plugins into a single control plane, and then grant access to only your limited set of users. If any other member control planes add a global plugin to their configuration, a conflict will result and prevent the changed configuration from being applied.

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
    Powering the API world

    Increase developer productivity, security, and performance at scale with the unified platform for API management, service mesh, and ingress controller.

    • Products
      • Kong Konnect
      • Kong Gateway Enterprise
      • Kong Gateway
      • Kong Mesh
      • Kong Ingress Controller
      • Kong Insomnia
      • Product Updates
      • Get Started
    • Documentation
      • Kong Konnect Docs
      • Kong Gateway Docs
      • Kong Gateway Enterprise Docs
      • Kong Mesh Docs
      • Kong Insomnia Docs
      • Kong Konnect Plugin Hub
    • Open Source
      • Kong Gateway
      • Kuma
      • Insomnia
      • Kong Community
    • Company
      • About Kong
      • Customers
      • Careers
      • Press
      • Events
      • Contact
  • Terms• Privacy• Trust and Compliance
© Kong Inc. 2023