apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "19323" uid: bf52c9d8-5964-4d65-9931-6460155e78bd spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-25T14:10:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099323ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 1.018981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 805.279µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:22:11Z" - latency: 991.613µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:21:11Z" - latency: 790.963µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:20:11Z" - latency: 938.061µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:19:11Z" - latency: 1.060275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:18:11Z" - latency: 892.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:17:11Z" - latency: 987.325µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:16:11Z" - latency: 1.066305ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:15:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "20567" uid: 543ac51d-d383-4946-a094-7c86ab53f3fa spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T14:09:11Z" message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.716867ms message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:27:11Z" - latency: 8.014796ms message: 'load-balancer-api-external: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:27:11Z" - latency: 5.248825ms message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:26:11Z" - latency: 8.027422ms message: 'load-balancer-api-external: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:26:11Z" - latency: 5.391224ms message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:25:11Z" - latency: 7.818452ms message: 'load-balancer-api-external: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:25:11Z" - latency: 5.307772ms message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 7.928736ms message: 'load-balancer-api-external: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:24:11Z" - latency: 5.509421ms message: 'load-balancer-api-external: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 10.046457ms message: 'load-balancer-api-external: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:23:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "20566" uid: c5663f75-57cb-4d3f-b9bd-d499e4a7236a spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-25T14:09:11Z" message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.382466ms message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:27:11Z" - latency: 8.061437ms message: 'load-balancer-api-internal: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:27:11Z" - latency: 5.773517ms message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:26:11Z" - latency: 8.006561ms message: 'load-balancer-api-internal: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:26:11Z" - latency: 5.381035ms message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:25:11Z" - latency: 7.844632ms message: 'load-balancer-api-internal: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:25:11Z" - latency: 5.286456ms message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 7.888294ms message: 'load-balancer-api-internal: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:24:11Z" - latency: 5.33378ms message: 'load-balancer-api-internal: tcp connection to a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 10.128072ms message: 'load-balancer-api-internal: resolved host name a2c97239a2eb64d5f947e0c1898996c5-d5abfbea8c058560.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-25T14:23:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-128-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "19322" uid: 996a4f57-be4d-4225-8d8a-8d6b079a5452 spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T14:10:11Z" message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.100621ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 2.079152ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 2.063789ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:22:11Z" - latency: 2.153341ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:21:11Z" - latency: 2.298856ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:20:11Z" - latency: 2.251664ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:19:11Z" - latency: 2.359982ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:18:11Z" - latency: 2.02105ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:17:11Z" - latency: 2.09338ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:16:11Z" - latency: 2.006221ms message: 'network-check-target-ip-10-0-128-220: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:15:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-132-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "19320" uid: 6a4274e4-5a1c-4eed-accc-62e211922f22 spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-25T14:10:11Z" message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 852.08µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 863.178µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 994.149µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:22:11Z" - latency: 732.54µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:21:11Z" - latency: 769.814µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:20:11Z" - latency: 876.34µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:19:11Z" - latency: 1.490911ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:18:11Z" - latency: 816.371µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:17:11Z" - latency: 903.42µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:16:11Z" - latency: 986.108µs message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:15:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-ip-10-0-133-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "19321" uid: 38b87658-9d2a-42ac-b547-aa908dd331e4 spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-25T14:10:11Z" message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.134397ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 1.991976ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 2.098383ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:22:11Z" - latency: 2.048123ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:21:11Z" - latency: 2.182305ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:20:11Z" - latency: 1.936297ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:19:11Z" - latency: 2.25781ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:18:11Z" - latency: 2.097926ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:17:11Z" - latency: 2.100508ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:16:11Z" - latency: 2.233491ms message: 'network-check-target-ip-10-0-133-35: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:15:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-25T14:03:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-134-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-134.ec2.internal uid: 025132f5-e0ed-4ba8-a321-e367e0412d34 resourceVersion: "20565" uid: b5a96ec6-d573-49ae-a515-612e6fb77356 spec: sourcePod: network-check-source-7f44b6dd87-kjb5f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-25T14:09:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.118093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:27:11Z" - latency: 1.61868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:27:11Z" - latency: 1.143092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:26:11Z" - latency: 1.608932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:26:11Z" - latency: 977.325µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:25:11Z" - latency: 1.789286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:25:11Z" - latency: 1.056408ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:24:11Z" - latency: 1.673159ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:24:11Z" - latency: 1.309691ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-25T14:23:11Z" - latency: 1.679545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-25T14:23:11Z" kind: List metadata: resourceVersion: ""