jichengzhi opened a new pull request, #113: URL: https://github.com/apache/skywalking-swck/pull/113
Related to [apache/skywalking#8937](https://github.com/apache/skywalking/issues/8937). The controller (`EventExporterReconciler`) maintains a deployment and a configMap for each EventExporter CR under the hood. If filters and exporters (`EventExporter.spec.data`) are updated, the controller compares current config to the previous one to identify an update: * prev config is empty and cur config is empty => no need to update * prev config is empty and cur config is not empty => create a new configMap with cur config * prev config is not empty and cur config is empty => delete the configMap * prev config is not empty and cur config is not empty * `prev config != cur config` => re-create the configMap with cur config * `prev config == cur config` => no need to update It is possible that the `EventExporter.Spec.Data` is empty if user ignores this field, in this case the event export will use the [default config](https://github.com/apache/skywalking-kubernetes-event-exporter/blob/9ad39c47eb347f13c0003d1ecd05c843c6d511ea/cmd/root.go#L50). If config is changed, the `md5-data` label value in the pod template (`Deployment.spec.template.metadata`) is updated, which will trigger a deployment update after the rendered template is applied. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
