apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "152668" uid: 54c1fdd4-364c-42f5-bf3a-8da13436f6fb spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T04:53:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.243233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 1.16403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 920.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:13Z" - latency: 983.402µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:13Z" - latency: 815.537µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:13Z" - latency: 1.253269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:13Z" - latency: 950.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:13Z" - latency: 776.274µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:13Z" - latency: 1.716578ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:13Z" - latency: 899.653µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "156911" uid: 2d33d85e-bd14-49d8-a885-6342cd4e9a06 spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T04:52:13Z" message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.744117ms message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:52:13Z" - latency: 6.264821ms message: 'load-balancer-api-external: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:52:13Z" - latency: 16.991876ms message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:51:13Z" - latency: 7.019692ms message: 'load-balancer-api-external: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:51:13Z" - latency: 14.076661ms message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:50:13Z" - latency: 6.509231ms message: 'load-balancer-api-external: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:50:13Z" - latency: 17.189251ms message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 7.121092ms message: 'load-balancer-api-external: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:49:13Z" - latency: 17.27685ms message: 'load-balancer-api-external: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 6.323587ms message: 'load-balancer-api-external: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:48:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "156912" uid: 82e4995b-f74b-4259-9f3e-b295be7ee087 spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T04:52:13Z" message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.278234ms message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:52:13Z" - latency: 6.171661ms message: 'load-balancer-api-internal: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:52:13Z" - latency: 17.131388ms message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:51:13Z" - latency: 7.078798ms message: 'load-balancer-api-internal: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:51:13Z" - latency: 14.078545ms message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:50:13Z" - latency: 6.440682ms message: 'load-balancer-api-internal: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:50:13Z" - latency: 17.198973ms message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 7.195223ms message: 'load-balancer-api-internal: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:49:13Z" - latency: 16.488169ms message: 'load-balancer-api-internal: tcp connection to a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 6.226696ms message: 'load-balancer-api-internal: resolved host name a04b35af0020c4f98a074f1b85a3c316-7a5978d4b1546e8c.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T05:48:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-134-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "152667" uid: 103da46c-e70d-4b70-8941-c5836ad51f77 spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T04:53:13Z" message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.617684ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 2.60415ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 2.35822ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:13Z" - latency: 2.47725ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:13Z" - latency: 2.480046ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:13Z" - latency: 2.675693ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:13Z" - latency: 2.60328ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:13Z" - latency: 2.221807ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:13Z" - latency: 2.762292ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:13Z" - latency: 2.025533ms message: 'network-check-target-ip-10-0-134-105: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-135-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "152665" uid: 66ab919c-77f9-4863-9c62-df196b36da71 spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T04:53:13Z" message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099256ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 2.456169ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 2.237508ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:13Z" - latency: 2.581402ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:13Z" - latency: 3.209426ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:13Z" - latency: 2.765118ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:13Z" - latency: 2.589021ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:13Z" - latency: 2.277575ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:13Z" - latency: 3.108268ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:13Z" - latency: 2.458787ms message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-network-check-target-ip-10-0-139-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "152664" uid: 7df10740-de95-4372-aad2-6eb9e17e0626 spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T04:53:13Z" message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.22321ms message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 1.129451ms message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 961.227µs message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:47:13Z" - latency: 1.627647ms message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:46:13Z" - latency: 790.936µs message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:45:13Z" - latency: 1.54558ms message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:44:13Z" - latency: 856.783µs message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:43:13Z" - latency: 955.374µs message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:42:13Z" - latency: 1.150263ms message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:41:13Z" - latency: 993.868µs message: 'network-check-target-ip-10-0-139-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:40:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T04:46:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-228.ec2.internal uid: aee9678e-56e1-4e56-9a2c-67c235552372 resourceVersion: "156909" uid: dc467aa4-c6be-4b9f-9c6e-37f0eae1978c spec: sourcePod: network-check-source-6f78d59f99-qxx47 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T04:52:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.073566ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:52:13Z" - latency: 1.826557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:52:13Z" - latency: 1.00895ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:51:13Z" - latency: 2.06201ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:51:13Z" - latency: 959.069µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:50:13Z" - latency: 1.71256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:50:13Z" - latency: 1.171292ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:49:13Z" - latency: 2.118103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:49:13Z" - latency: 1.127161ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T05:48:13Z" - latency: 1.906077ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T05:48:13Z" kind: List metadata: resourceVersion: ""