apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "22977" uid: 9b5c46b9-d0a0-4488-b5d4-d068a5f38ed3 spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T06:01:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:15:13Z" - latency: 1.125512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:14:13Z" - latency: 1.432985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:13:13Z" - latency: 839.646µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 1.595979ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 1.373409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 804.553µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 1.063588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 948.025µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:07:13Z" - latency: 874.802µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:06:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "21547" uid: dc9e3369-c05f-425c-9817-1fdd8f088671 spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T06:00:13Z" message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.921382ms message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 6.608266ms message: 'load-balancer-api-external: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:12:13Z" - latency: 5.623521ms message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 7.018546ms message: 'load-balancer-api-external: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:11:13Z" - latency: 5.314093ms message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 7.388215ms message: 'load-balancer-api-external: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:10:13Z" - latency: 4.97575ms message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 7.868331ms message: 'load-balancer-api-external: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:09:13Z" - latency: 5.285452ms message: 'load-balancer-api-external: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 7.188124ms message: 'load-balancer-api-external: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "21546" uid: 1a450bf9-85ff-4cf5-b962-f6c79b56d5fa spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T06:00:13Z" message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.966015ms message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 6.535523ms message: 'load-balancer-api-internal: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:12:13Z" - latency: 5.623873ms message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 6.991433ms message: 'load-balancer-api-internal: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:11:13Z" - latency: 5.318348ms message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 7.295568ms message: 'load-balancer-api-internal: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:10:13Z" - latency: 4.975286ms message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 7.793852ms message: 'load-balancer-api-internal: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:09:13Z" - latency: 5.248189ms message: 'load-balancer-api-internal: tcp connection to a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 7.0835ms message: 'load-balancer-api-internal: resolved host name a43d1690dbaae47eda4f64e502d93003-eeeb6593e78bdc97.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T06:08:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-135-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "22975" uid: 40fbf66d-421b-4d8a-a147-423c4f2602ae spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:01:13Z" message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.501182ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:15:13Z" - latency: 2.432292ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:14:13Z" - latency: 2.166767ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:13:13Z" - latency: 2.17039ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 2.283167ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 2.437909ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 2.280809ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 2.219203ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 2.327076ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:07:13Z" - latency: 1.897995ms message: 'network-check-target-ip-10-0-135-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:06:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-136-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "22976" uid: cff6029b-b028-415c-ac41-c55f8deab714 spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:01:13Z" message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365028ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:15:13Z" - latency: 2.306211ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:14:13Z" - latency: 2.862981ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:13:13Z" - latency: 2.321272ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 3.081879ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 2.261419ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 2.15281ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 2.192381ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 2.144999ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:07:13Z" - latency: 2.277391ms message: 'network-check-target-ip-10-0-136-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:06:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-ip-10-0-140-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "22974" uid: 442cc408-f225-413f-836e-5e9deb5e0770 spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T06:01:13Z" message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004005ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:15:13Z" - latency: 1.397102ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:14:13Z" - latency: 952.347µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:13:13Z" - latency: 978.727µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 918.864µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 887.218µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 1.364038ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 1.040617ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 970.198µs message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:07:13Z" - latency: 1.442365ms message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:06:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T05:54:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-64.ec2.internal uid: 5f874700-872a-413c-9071-a706321e7deb resourceVersion: "21544" uid: 7116ece0-e5fd-4210-a096-59f0c23a877f spec: sourcePod: network-check-source-6947749cfc-9hwj9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T06:00:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:12:13Z" - latency: 1.714239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:12:13Z" - latency: 872.25µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:11:13Z" - latency: 1.818922ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:11:13Z" - latency: 944.196µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:10:13Z" - latency: 2.268349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:10:13Z" - latency: 809.639µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:09:13Z" - latency: 2.184592ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:09:13Z" - latency: 827.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T06:08:13Z" - latency: 2.128408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T06:08:13Z" kind: List metadata: resourceVersion: ""