CONTROLPLANE ALTERNATIVE UPGRADE

During rolling upgrade of the 2nd round, controller to brokers traffic will start using the ' ', and go through the proposed changes in this KIP. 'CONTROLLER' and set ' .requests.enable=true' if the control plane is required to force the validation of the control request. In the 2nd round, the ' ' config should be set to the corresponding listener name, e.g. After the first round is completed, controller to brokers communication should still behave in the same way that uses the inter-broker-listener-name, since the ' ' is not set yet. Specifically, an endpoint with the controller listener name should be added to the 'listeners' config, e.g. ' CONTROLLER://192.1.1.8:9091' if the 'advertised.listeners' config is explicitly configured and is not getting its value from 'listeners', the new endpoint for controller should also be added to 'advertised.listeners'. The goal of the first round is to add the controller endpoint, without adding the ' ' config. Migration plan: 2 rounds of rolling upgrades are needed to pick up the proposed changes in this KIP.Impacts: Controller-related requests will be made entirely through the control plane,and completely separate control requests from data requests.If .requests.enable is true, the control plane should allow only four kinds of requests: LeaderAndIsrRequest, UpdateMetadataRequest,StopReplicaRequest,C ontrolledShutdownRequest.ĬonnectionQueueSize: Int = ConnectionQueueSize,Ĭompatibility, Deprecation, and Migration Plan ' .requests.enable' is disabled by default.The default control plane does not reject data requests, which can remain compatible when the user uses the control plane for data requests. .requests.enable : If this configuration is true, the control plane will reject data requests completely, default is false.Īdd isControlPlane to the constructor of the processor, this value is passed in when the processor associated with the data plane and the control plane is created.It has a highly extensible backend that enables you to build a control plane that can orchestrate applications and infrastructure no matter where they run, and a highly configurable frontend that puts you in control of the schema of the declarative API it offers. So We need to provide a way for the control plane to reject data requests.Īlso, when the control plane is enabled, the broker needs to communicate with the controller using the control plane to send the controlledShutdown request.Īdd an optional configuration on the broker side: Crossplane is a framework for building cloud native control planes without needing to write code. When the user administrator wants to deny the data request access control plane completely, this cannot be done now. Whether it is used unintentionally or intentionally, this is the problem faced by the current control plane. The client can define the 'bootstrap-servers' as the control plane,this causes the control plane regresses to the data plane.This would violate the design work of KIP-291. Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).Īt present,data requests and control requests use different endpoints,these endpoints are all registered to ZooKeeper.

Controlplane alternative