Cilium v1.7 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls each client workload to also trust this new certificate, otherwise the client’s TLS library will reject the connection as invalid. In this model, the network firewall uses the certificate signed by the 10:53:40.147 Channel ipv4 State: DOWN Input filter: ACCEPT Output filter: REJECT ... Basic configuration It’s hard to discuss bird configurations without considering specific0 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.10 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls each client workload to also trust this new certificate, otherwise the client’s TLS library will reject the connection as invalid. In this model, the network firewall uses the certificate signed by the 10:53:40.147 Channel ipv4 State: DOWN Input filter: ACCEPT Output filter: REJECT ... Basic configuration It’s hard to discuss bird configurations without considering specific0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.8 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls each client workload to also trust this new certificate, otherwise the client’s TLS library will reject the connection as invalid. In this model, the network firewall uses the certificate signed by the 10:53:40.147 Channel ipv4 State: DOWN Input filter: ACCEPT Output filter: REJECT ... Basic configuration It’s hard to discuss bird configurations without considering specific0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.11 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls each client workload to also trust this new certificate, otherwise the client’s TLS library will reject the connection as invalid. In this model, the network firewall uses the certificate signed by the 10:53:40.147 Channel ipv4 State: DOWN Input filter: ACCEPT Output filter: REJECT ... Basic configuration It’s hard to discuss bird configurations without considering specific0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.9 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls each client workload to also trust this new certificate, otherwise the client’s TLS library will reject the connection as invalid. In this model, the network firewall uses the certificate signed by the 10:53:40.147 Channel ipv4 State: DOWN Input filter: ACCEPT Output filter: REJECT ... Basic configuration It’s hard to discuss bird configurations without considering specific0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.6 Documentationother requests. Allow service1 to produce on Kafka topic topic1 and service2 to consume on topic1. Reject all other Kafka messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls instance as its userspace proxy. Envoy will then either forward the traffic or generate appropriate reject messages based on the configured L7 policy. These components are connected to create the flexible 4.10 or earlier When a CIDR policy with too many unique prefix lengths is imported, Cilium will reject the policy with a message like the following: $ cilium policy import too_many_cidrs.json Error:0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.5 Documentationrequests. Allow service1 to produce on Ka�a topic topic1 and service2 to consume on topic1 . Reject all other Ka�a messages. Require the HTTP header X-Token: [0-9]+ to be present in all REST calls instance as its userspace proxy. Envoy will then either forward the traffic or generate appropriate reject messages based on the configured L7 policy. These components are connected to create the flexible 4.10 or earlier When a CIDR policy with too many unique prefix lengths is imported, Cilium will reject the policy with a message like the following: Cilium 1.0 Cilium 1.1 or later $ cilium policy import0 码力 | 740 页 | 12.52 MB | 1 年前3
共 7 条
- 1













