apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "46623" uid: 56483c54-9de1-4192-95c4-1fcaa2b19bef spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T23:13:58Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.093511ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 1.004372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 1.118023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 1.216584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:31:58Z" - latency: 1.06522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:30:58Z" - latency: 1.294216ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:29:58Z" - latency: 975.311µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:28:58Z" - latency: 995.874µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:27:58Z" - latency: 905.399µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:26:58Z" - latency: 982.375µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:25:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "48964" uid: f6552c55-fa84-412f-ae87-ec2854a260ec spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T23:12:58Z" message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.80514ms message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:36:58Z" - latency: 8.55183ms message: 'load-balancer-api-external: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:36:58Z" - latency: 4.897624ms message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:35:58Z" - latency: 8.19589ms message: 'load-balancer-api-external: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:35:58Z" - latency: 4.835996ms message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 17.995282ms message: 'load-balancer-api-external: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:34:58Z" - latency: 5.259791ms message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 8.53672ms message: 'load-balancer-api-external: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:33:58Z" - latency: 4.907669ms message: 'load-balancer-api-external: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 12.346158ms message: 'load-balancer-api-external: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:32:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "48965" uid: 0a19a5e5-7d8a-4a84-97f6-1b59716b33bc spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T23:12:58Z" message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.851197ms message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:36:58Z" - latency: 8.469158ms message: 'load-balancer-api-internal: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:36:58Z" - latency: 4.906213ms message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:35:58Z" - latency: 8.124168ms message: 'load-balancer-api-internal: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:35:58Z" - latency: 4.805389ms message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 17.886691ms message: 'load-balancer-api-internal: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:34:58Z" - latency: 3.972146ms message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 8.447598ms message: 'load-balancer-api-internal: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:33:58Z" - latency: 4.897501ms message: 'load-balancer-api-internal: tcp connection to a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 12.262915ms message: 'load-balancer-api-internal: resolved host name a1066d0682eca4ac8ada662375600a29-3c619c2c821195f0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T23:32:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-network-check-target-ip-10-0-133-43 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "46621" uid: c9a9c6e8-eb13-4702-a0b6-e050a3ee9d66 spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:13:58Z" message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312113ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 2.767835ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 2.150947ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 2.175869ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:31:58Z" - latency: 2.271749ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:30:58Z" - latency: 2.300496ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:29:58Z" - latency: 2.407778ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:28:58Z" - latency: 2.146131ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:27:58Z" - latency: 2.339683ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:26:58Z" - latency: 2.451569ms message: 'network-check-target-ip-10-0-133-43: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:25:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-network-check-target-ip-10-0-134-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "46622" uid: 9153c2e0-a7d4-4de7-97df-9427fac4453d spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:13:58Z" message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.7682ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 2.603579ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 2.301689ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 2.263761ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:31:58Z" - latency: 2.326688ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:30:58Z" - latency: 2.18443ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:29:58Z" - latency: 2.409387ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:28:58Z" - latency: 2.465573ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:27:58Z" - latency: 2.456599ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:26:58Z" - latency: 2.300136ms message: 'network-check-target-ip-10-0-134-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:25:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-network-check-target-ip-10-0-138-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "46620" uid: e0a0cfc7-ee67-4ab0-ad3b-e4a1ff0cad74 spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T23:13:58Z" message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.47631ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 979.77µs message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 1.167205ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 1.52228ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:31:58Z" - latency: 922.574µs message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:30:58Z" - latency: 959.401µs message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:29:58Z" - latency: 1.232882ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:28:58Z" - latency: 1.18033ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:27:58Z" - latency: 1.226913ms message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:26:58Z" - latency: 883.706µs message: 'network-check-target-ip-10-0-138-203: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:25:58Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T23:06:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-203.ec2.internal uid: ca5671b1-67eb-442e-814f-12e78d18a94e resourceVersion: "48962" uid: 6bb340bd-63a7-4502-a40b-6b4df869f472 spec: sourcePod: network-check-source-dbd9cf844-7r55r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T23:12:58Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:36:58Z" - latency: 1.652853ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:36:58Z" - latency: 770.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:35:58Z" - latency: 1.819463ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:35:58Z" - latency: 1.020105ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:34:58Z" - latency: 1.667216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:34:58Z" - latency: 1.36959ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:33:58Z" - latency: 1.716294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:33:58Z" - latency: 973.383µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T23:32:58Z" - latency: 1.953296ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T23:32:58Z" kind: List metadata: resourceVersion: ""