@@ -319,6 +319,112 @@ entries:
319
319
urls:
320
320
- cilium-1.17.0-pre.0.tgz
321
321
version: 1.17.0-pre.0
322
+ - annotations:
323
+ artifacthub.io/crds: "- kind: CiliumNetworkPolicy\n version: v2\n name: ciliumnetworkpolicies.cilium.io\n
324
+ \ displayName: Cilium Network Policy\n description: |\n Cilium Network
325
+ Policies provide additional functionality beyond what\n is provided by
326
+ standard Kubernetes NetworkPolicy such as the ability\n to allow traffic
327
+ based on FQDNs, or to filter at Layer 7.\n- kind: CiliumClusterwideNetworkPolicy\n
328
+ \ version: v2\n name: ciliumclusterwidenetworkpolicies.cilium.io\n displayName:
329
+ Cilium Clusterwide Network Policy\n description: |\n Cilium Clusterwide
330
+ Network Policies support configuring network traffic\n policiies across
331
+ the entire cluster, including applying node firewalls.\n- kind: CiliumExternalWorkload\n
332
+ \ version: v2\n name: ciliumexternalworkloads.cilium.io\n displayName: Cilium
333
+ External Workload\n description: |\n Cilium External Workload supports
334
+ configuring the ability for external\n non-Kubernetes workloads to join
335
+ the cluster.\n- kind: CiliumLocalRedirectPolicy\n version: v2\n name: ciliumlocalredirectpolicies.cilium.io\n
336
+ \ displayName: Cilium Local Redirect Policy\n description: |\n Cilium
337
+ Local Redirect Policy allows local redirects to be configured\n within
338
+ a node to support use cases like Node-Local DNS or KIAM.\n- kind: CiliumNode\n
339
+ \ version: v2\n name: ciliumnodes.cilium.io\n displayName: Cilium Node\n
340
+ \ description: |\n Cilium Node represents a node managed by Cilium. It
341
+ contains a\n specification to control various node specific configuration
342
+ aspects\n and a status section to represent the status of the node.\n-
343
+ kind: CiliumIdentity\n version: v2\n name: ciliumidentities.cilium.io\n
344
+ \ displayName: Cilium Identity\n description: |\n Cilium Identity allows
345
+ introspection into security identities that\n Cilium allocates which identify
346
+ sets of labels that are assigned to\n individual endpoints in the cluster.\n-
347
+ kind: CiliumEndpoint\n version: v2\n name: ciliumendpoints.cilium.io\n displayName:
348
+ Cilium Endpoint\n description: |\n Cilium Endpoint represents the status
349
+ of individual pods or nodes in\n the cluster which are managed by Cilium,
350
+ including enforcement status,\n IP addressing and whether the networking
351
+ is successfully operational.\n- kind: CiliumEndpointSlice\n version: v2alpha1\n
352
+ \ name: ciliumendpointslices.cilium.io\n displayName: Cilium Endpoint Slice\n
353
+ \ description: |\n Cilium Endpoint Slice represents the status of groups
354
+ of pods or nodes\n in the cluster which are managed by Cilium, including
355
+ enforcement status,\n IP addressing and whether the networking is successfully
356
+ operational.\n- kind: CiliumEgressGatewayPolicy\n version: v2\n name: ciliumegressgatewaypolicies.cilium.io\n
357
+ \ displayName: Cilium Egress Gateway Policy\n description: |\n Cilium
358
+ Egress Gateway Policy provides control over the way that traffic\n leaves
359
+ the cluster and which source addresses to use for that traffic.\n- kind: CiliumClusterwideEnvoyConfig\n
360
+ \ version: v2\n name: ciliumclusterwideenvoyconfigs.cilium.io\n displayName:
361
+ Cilium Clusterwide Envoy Config\n description: |\n Cilium Clusterwide
362
+ Envoy Config specifies Envoy resources and K8s service mappings\n to be
363
+ provisioned into Cilium host proxy instances in cluster context.\n- kind:
364
+ CiliumEnvoyConfig\n version: v2\n name: ciliumenvoyconfigs.cilium.io\n displayName:
365
+ Cilium Envoy Config\n description: |\n Cilium Envoy Config specifies Envoy
366
+ resources and K8s service mappings\n to be provisioned into Cilium host
367
+ proxy instances in namespace context.\n- kind: CiliumBGPPeeringPolicy\n version:
368
+ v2alpha1\n name: ciliumbgppeeringpolicies.cilium.io\n displayName: Cilium
369
+ BGP Peering Policy\n description: |\n Cilium BGP Peering Policy instructs
370
+ Cilium to create specific BGP peering\n configurations.\n- kind: CiliumBGPClusterConfig\n
371
+ \ version: v2alpha1\n name: ciliumbgpclusterconfigs.cilium.io\n displayName:
372
+ Cilium BGP Cluster Config\n description: |\n Cilium BGP Cluster Config
373
+ instructs Cilium operator to create specific BGP cluster\n configurations.\n-
374
+ kind: CiliumBGPPeerConfig\n version: v2alpha1\n name: ciliumbgppeerconfigs.cilium.io\n
375
+ \ displayName: Cilium BGP Peer Config\n description: |\n CiliumBGPPeerConfig
376
+ is a common set of BGP peer configurations. It can be referenced \n by
377
+ multiple peers from CiliumBGPClusterConfig.\n- kind: CiliumBGPAdvertisement\n
378
+ \ version: v2alpha1\n name: ciliumbgpadvertisements.cilium.io\n displayName:
379
+ Cilium BGP Advertisement\n description: |\n CiliumBGPAdvertisement is
380
+ used to define source of BGP advertisement as well as BGP attributes \n to
381
+ be advertised with those prefixes.\n- kind: CiliumBGPNodeConfig\n version:
382
+ v2alpha1\n name: ciliumbgpnodeconfigs.cilium.io\n displayName: Cilium BGP
383
+ Node Config\n description: |\n CiliumBGPNodeConfig is read only node specific
384
+ BGP configuration. It is constructed by Cilium operator.\n It will also
385
+ contain node local BGP state information.\n- kind: CiliumBGPNodeConfigOverride\n
386
+ \ version: v2alpha1\n name: ciliumbgpnodeconfigoverrides.cilium.io\n displayName:
387
+ Cilium BGP Node Config Override\n description: |\n CiliumBGPNodeConfigOverride
388
+ can be used to override node specific BGP configuration.\n- kind: CiliumLoadBalancerIPPool\n
389
+ \ version: v2alpha1\n name: ciliumloadbalancerippools.cilium.io\n displayName:
390
+ Cilium Load Balancer IP Pool\n description: |\n Defining a Cilium Load
391
+ Balancer IP Pool instructs Cilium to assign IPs to LoadBalancer Services.\n-
392
+ kind: CiliumNodeConfig\n version: v2alpha1\n name: ciliumnodeconfigs.cilium.io\n
393
+ \ displayName: Cilium Node Configuration\n description: |\n CiliumNodeConfig
394
+ is a list of configuration key-value pairs. It is applied to\n nodes indicated
395
+ by a label selector.\n- kind: CiliumCIDRGroup\n version: v2alpha1\n name:
396
+ ciliumcidrgroups.cilium.io\n displayName: Cilium CIDR Group\n description:
397
+ |\n CiliumCIDRGroup is a list of CIDRs that can be referenced as a single
398
+ entity from CiliumNetworkPolicies.\n- kind: CiliumL2AnnouncementPolicy\n version:
399
+ v2alpha1\n name: ciliuml2announcementpolicies.cilium.io\n displayName: Cilium
400
+ L2 Announcement Policy\n description: |\n CiliumL2AnnouncementPolicy is
401
+ a policy which determines which service IPs will be announced to\n the
402
+ local area network, by which nodes, and via which interfaces.\n- kind: CiliumPodIPPool\n
403
+ \ version: v2alpha1\n name: ciliumpodippools.cilium.io\n displayName: Cilium
404
+ Pod IP Pool\n description: |\n CiliumPodIPPool defines an IP pool that
405
+ can be used for pooled IPAM (i.e. the multi-pool IPAM mode).\n"
406
+ apiVersion: v2
407
+ appVersion: 1.16.4
408
+ created: "2024-11-20T09:05:38.752908124Z"
409
+ description: eBPF-based Networking, Security, and Observability
410
+ digest: e96a1fba0f361926bb29e6bc2fe565d5fe36be9c5194fad85e8ed2e828d09864
411
+ home: https://cilium.io/
412
+ icon: https://cdn.jsdelivr.net/gh/cilium/cilium@main/Documentation/images/logo-solo.svg
413
+ keywords:
414
+ - BPF
415
+ - eBPF
416
+ - Kubernetes
417
+ - Networking
418
+ - Security
419
+ - Observability
420
+ - Troubleshooting
421
+ kubeVersion: '>= 1.21.0-0'
422
+ name: cilium
423
+ sources:
424
+ - https://github.com/cilium/cilium
425
+ urls:
426
+ - cilium-1.16.4.tgz
427
+ version: 1.16.4
322
428
- annotations:
323
429
artifacthub.io/crds: "- kind: CiliumNetworkPolicy\n version: v2\n name: ciliumnetworkpolicies.cilium.io\n
324
430
\ displayName: Cilium Network Policy\n description: |\n Cilium Network
@@ -20911,4 +21017,4 @@ entries:
20911
21017
urls:
20912
21018
- tetragon-0.8.0.tgz
20913
21019
version: 0.8.0
20914
- generated: "2024-11-20T09:15:29.562656717Z "
21020
+ generated: "2024-11-20T09:05:38.745175782Z "
0 commit comments