如何基于fabric8 Kubernetes客户端实现全自定义资源Informer？

错误原因 #

直接使用GenericKubernetesResource.class调用resources()方法会触发客户端类型检查报错，因为客户端无法从泛型类型中获取具体的CustomResourceDefinition（CRD）元数据（组、版本、Kind），必须明确指定目标CRD的元信息才能创建合法的Informer。

解决方案 #

方案一：遍历所有CRD，为每个CRD创建对应的GenericKubernetesResource Informer #

通过先获取集群中所有CRD，再逐个为每个CRD注册对应的Informer，实现对所有自定义资源的监听：

import io.fabric8.kubernetes.api.model.apiextensions.v1.CustomResourceDefinition;
import io.fabric8.kubernetes.client.inform.SharedIndexInformer;
import io.fabric8.kubernetes.client.inform.ResourceEventHandler;
import io.fabric8.kubernetes.client.dsl.GenericKubernetesResourceOperations;
import java.util.HashMap;
import java.util.Map;

// 1. 监听CRD变化，实时注册/更新Informer
SharedIndexInformer<CustomResourceDefinition> crdInformer = client.customResourceDefinitions().inform();
// 存储已注册的Informer，方便后续注销
Map<String, SharedIndexInformer<GenericKubernetesResource>> informerMap = new HashMap<>();

crdInformer.addEventHandler(new ResourceEventHandler<CustomResourceDefinition>() {
    @Override
    public void onAdd(CustomResourceDefinition crd) {
        registerCRDInformer(crd);
    }

    @Override
    public void onUpdate(CustomResourceDefinition oldCrd, CustomResourceDefinition newCrd) {
        // 先注销旧Informer
        String key = generateCRDKey(oldCrd);
        informerMap.get(key).stop();
        informerMap.remove(key);
        // 注册新Informer
        registerCRDInformer(newCrd);
    }

    @Override
    public void onDelete(CustomResourceDefinition crd, boolean deletedFinalStateUnknown) {
        String key = generateCRDKey(crd);
        SharedIndexInformer<GenericKubernetesResource> informer = informerMap.remove(key);
        if (informer != null) {
            informer.stop();
        }
    }
});

// 注册单个CRD对应的Informer
private void registerCRDInformer(CustomResourceDefinition crd) {
    String group = crd.getSpec().getGroup();
    // 选取CRD的第一个可用版本，可根据业务需求调整
    String version = crd.getSpec().getVersions().get(0).getName();
    String kind = crd.getSpec().getNames().getKind();

    // 创建指定CRD元数据的GenericKubernetesResource操作对象
    GenericKubernetesResourceOperations resourceOps = client.genericKubernetesResources(group, version, kind);
    // 创建Informer并绑定事件处理器
    SharedIndexInformer<GenericKubernetesResource> informer = resourceOps
            .inNamespace(kubernetesClientConfig.getConfig().getNamespace())
            .inform(myHandler, 60 * 1000L);
    // 存入Map管理
    informerMap.put(generateCRDKey(crd), informer);
}

// 生成CRD的唯一标识Key
private String generateCRDKey(CustomResourceDefinition crd) {
    return crd.getSpec().getGroup() + "/" + crd.getSpec().getNames().getKind();
}

方案二：使用DynamicClient结合Unstructured类型监听 #

利用Fabric8的DynamicClient，通过Unstructured类型处理任意自定义资源，再转换为GenericKubernetesResource：

import io.fabric8.kubernetes.api.model.apiextensions.v1.CustomResourceDefinition;
import io.fabric8.kubernetes.client.DynamicClient;
import io.fabric8.kubernetes.client.inform.SharedIndexInformer;
import io.fabric8.kubernetes.client.inform.ResourceEventHandler;
import io.fabric8.kubernetes.api.model.Unstructured;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

DynamicClient dynamicClient = client.adapt(DynamicClient.class);
Map<String, SharedIndexInformer<Unstructured>> informerMap = new HashMap<>();

// 获取所有已存在的CRD并注册Informer
List<CustomResourceDefinition> crds = client.customResourceDefinitions().list().getItems();
for (CustomResourceDefinition crd : crds) {
    registerDynamicInformer(crd);
}

// 监听CRD变化，同步更新Informer
client.customResourceDefinitions().inform(new ResourceEventHandler<CustomResourceDefinition>() {
    @Override
    public void onAdd(CustomResourceDefinition crd) {
        registerDynamicInformer(crd);
    }

    @Override
    public void onUpdate(CustomResourceDefinition oldCrd, CustomResourceDefinition newCrd) {
        String key = generateCRDKey(oldCrd);
        informerMap.get(key).stop();
        informerMap.remove(key);
        registerDynamicInformer(newCrd);
    }

    @Override
    public void onDelete(CustomResourceDefinition crd, boolean deletedFinalStateUnknown) {
        String key = generateCRDKey(crd);
        SharedIndexInformer<Unstructured> informer = informerMap.remove(key);
        if (informer != null) {
            informer.stop();
        }
    }
});

// 注册DynamicClient的Informer
private void registerDynamicInformer(CustomResourceDefinition crd) {
    String group = crd.getSpec().getGroup();
    String version = crd.getSpec().getVersions().get(0).getName();
    String plural = crd.getSpec().getNames().getPlural();

    Resource<Unstructured> resource = dynamicClient.resources(group, version, plural);
    SharedIndexInformer<Unstructured> informer = resource
            .inNamespace(kubernetesClientConfig.getConfig().getNamespace())
            .inform(new ResourceEventHandler<Unstructured>() {
                @Override
                public void onAdd(Unstructured resource) {
                    GenericKubernetesResource gkr = GenericKubernetesResource.fromUnstructured(resource);
                    myHandler.onAdd(gkr);
                }

                @Override
                public void onUpdate(Unstructured oldResource, Unstructured newResource) {
                    GenericKubernetesResource oldGkr = GenericKubernetesResource.fromUnstructured(oldResource);
                    GenericKubernetesResource newGkr = GenericKubernetesResource.fromUnstructured(newResource);
                    myHandler.onUpdate(oldGkr, newGkr);
                }

                @Override
                public void onDelete(Unstructured resource, boolean deletedFinalStateUnknown) {
                    GenericKubernetesResource gkr = GenericKubernetesResource.fromUnstructured(resource);
                    myHandler.onDelete(gkr, deletedFinalStateUnknown);
                }
            }, 60 * 1000L);
    informerMap.put(generateCRDKey(crd), informer);
}

private String generateCRDKey(CustomResourceDefinition crd) {
    return crd.getSpec().getGroup() + "/" + crd.getSpec().getNames().getKind();
}

注意事项 #

• 内存管理：必须维护Informer的映射集合，在CRD更新或删除时及时停止并移除对应的Informer，避免内存泄漏。
• 命名空间范围：如果需要监听所有命名空间的自定义资源，可移除inNamespace()调用，或传入NamespaceAll常量。
• 权限控制：确保Kubernetes客户端拥有customresourcedefinitions的读取权限，以及所有自定义资源的监听权限。

内容的提问来源于stack exchange，提问作者Lobo