apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "45671" uid: e6cf8999-8e2a-44ef-bdfb-49f7e9731991 spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-07T09:20:56Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.849981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 990.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 973.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 2.033727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:38:56Z" - latency: 1.132069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:37:56Z" - latency: 1.93655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:36:56Z" - latency: 1.178474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:35:56Z" - latency: 917.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:34:56Z" - latency: 930.17µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:33:56Z" - latency: 1.169676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "47738" uid: eaa727d1-4066-40d1-8fcb-39a5473145db spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T09:19:56Z" message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.937877ms message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:43:56Z" - latency: 7.96675ms message: 'load-balancer-api-external: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:43:56Z" - latency: 3.164988ms message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:42:56Z" - latency: 8.982537ms message: 'load-balancer-api-external: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:42:56Z" - latency: 4.688407ms message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 9.44496ms message: 'load-balancer-api-external: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:41:56Z" - latency: 3.976073ms message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 8.895902ms message: 'load-balancer-api-external: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:40:56Z" - latency: 4.305703ms message: 'load-balancer-api-external: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 14.080621ms message: 'load-balancer-api-external: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:39:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "47737" uid: 196ab27f-fa8b-4200-a8fc-bde4fe54340c spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-07T09:19:56Z" message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.147182ms message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:43:56Z" - latency: 7.945514ms message: 'load-balancer-api-internal: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:43:56Z" - latency: 2.922159ms message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:42:56Z" - latency: 8.953464ms message: 'load-balancer-api-internal: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:42:56Z" - latency: 4.691255ms message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 9.429352ms message: 'load-balancer-api-internal: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:41:56Z" - latency: 4.833332ms message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 8.894072ms message: 'load-balancer-api-internal: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:40:56Z" - latency: 4.349416ms message: 'load-balancer-api-internal: tcp connection to aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 14.056061ms message: 'load-balancer-api-internal: resolved host name aa24a71fc0be9492abbfa70c713094c9-daeb0e934cf66822.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-07T09:39:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-128-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "45669" uid: 00a4c77d-6024-4344-951f-056b806a5019 spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-07T09:20:56Z" message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.470716ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 2.404907ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 2.370859ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 3.109165ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:38:56Z" - latency: 2.440984ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:37:56Z" - latency: 2.249224ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:36:56Z" - latency: 2.272119ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:35:56Z" - latency: 2.356727ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:34:56Z" - latency: 2.40948ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:33:56Z" - latency: 2.55208ms message: 'network-check-target-ip-10-0-128-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-129-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "45668" uid: c3f3b00a-84eb-4471-bdc5-c8a84cfa8f01 spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-07T09:20:56Z" message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099789ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 1.290699ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 909.17µs message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 2.521687ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:38:56Z" - latency: 1.329953ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:37:56Z" - latency: 997.245µs message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:36:56Z" - latency: 1.37583ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:35:56Z" - latency: 1.595966ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:34:56Z" - latency: 917.902µs message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:33:56Z" - latency: 1.709119ms message: 'network-check-target-ip-10-0-129-203: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-network-check-target-ip-10-0-134-51 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "45670" uid: fdbdadfe-6eaa-4edc-9a0f-95e63123b2b2 spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-07T09:20:56Z" message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.874945ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 1.838402ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 2.138876ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 2.813137ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:38:56Z" - latency: 2.105337ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:37:56Z" - latency: 2.696858ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:36:56Z" - latency: 2.077824ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:35:56Z" - latency: 2.742993ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:34:56Z" - latency: 2.613446ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:33:56Z" - latency: 2.497864ms message: 'network-check-target-ip-10-0-134-51: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:32:56Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-07T09:13:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-203-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-203.ec2.internal uid: 8e702270-029f-4772-b8b2-bc9efd0251cf resourceVersion: "47736" uid: 037e2267-5418-4d9c-98fe-c4db0acc0902 spec: sourcePod: network-check-source-dbd9cf844-9wmd7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-07T09:19:56Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.264µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:43:56Z" - latency: 1.86945ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T09:43:56Z" - latency: 780.001µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:42:56Z" - latency: 2.208756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T09:42:56Z" - latency: 1.344663ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:41:56Z" - latency: 2.100759ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T09:41:56Z" - latency: 804.783µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:40:56Z" - latency: 1.819847ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T09:40:56Z" - latency: 886.831µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-07T09:39:56Z" - latency: 1.678491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-07T09:39:56Z" kind: List metadata: resourceVersion: ""