apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "39785" uid: 29261db5-a2a0-4e08-b3d4-287596b63f3e spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:58:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.607µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 843.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:22Z" - latency: 920.49µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:22Z" - latency: 962.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:22Z" - latency: 1.140108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:22Z" - latency: 1.343767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:22Z" - latency: 921.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:22Z" - latency: 1.023592ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:22Z" - latency: 925.942µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:22Z" - latency: 1.037789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "41851" uid: 92238729-8416-4ad2-83c5-90631676b0cf spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:57:22Z" message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.650017ms message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:22Z" - latency: 7.345368ms message: 'load-balancer-api-external: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:51:22Z" - latency: 5.022167ms message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:22Z" - latency: 6.67457ms message: 'load-balancer-api-external: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:50:22Z" - latency: 3.377836ms message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:22Z" - latency: 5.70566ms message: 'load-balancer-api-external: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:49:22Z" - latency: 2.938336ms message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:22Z" - latency: 6.540554ms message: 'load-balancer-api-external: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:22Z" - latency: 3.858687ms message: 'load-balancer-api-external: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 6.749204ms message: 'load-balancer-api-external: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "41850" uid: c8b0e02f-d5e2-4530-a08c-c68546fd4230 spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:57:22Z" message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.71734ms message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:22Z" - latency: 7.292025ms message: 'load-balancer-api-internal: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:51:22Z" - latency: 5.014847ms message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:22Z" - latency: 6.693605ms message: 'load-balancer-api-internal: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:50:22Z" - latency: 4.517555ms message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:22Z" - latency: 5.736337ms message: 'load-balancer-api-internal: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:49:22Z" - latency: 3.833521ms message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:22Z" - latency: 6.617492ms message: 'load-balancer-api-internal: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:22Z" - latency: 3.621974ms message: 'load-balancer-api-internal: tcp connection to af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 6.691731ms message: 'load-balancer-api-internal: resolved host name af2f49ad88e0c40219fa5bb2645ef118-8d5ba8e97fbf2710.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-129-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "39783" uid: 901c6001-15cd-46df-9126-359be77becfc spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:22Z" message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.802757ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 1.809547ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:22Z" - latency: 1.762644ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:22Z" - latency: 1.416486ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:22Z" - latency: 1.642786ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:22Z" - latency: 2.088867ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:22Z" - latency: 2.012245ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:22Z" - latency: 1.883214ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:22Z" - latency: 1.685516ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:22Z" - latency: 1.96842ms message: 'network-check-target-ip-10-0-129-249: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-133-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "39782" uid: 8316e731-a56e-48a6-a385-88bf10496ebb spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:22Z" message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 721.249µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 848.515µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:22Z" - latency: 673.888µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:22Z" - latency: 699.74µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:22Z" - latency: 795.691µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:22Z" - latency: 810.058µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:22Z" - latency: 849.726µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:22Z" - latency: 751.2µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:22Z" - latency: 778.331µs message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:22Z" - latency: 1.190324ms message: 'network-check-target-ip-10-0-133-163: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-network-check-target-ip-10-0-137-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "39784" uid: 45ecb45c-1bf8-4fda-acc2-c5cf9580b25c spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:58:22Z" message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.140649ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 1.924408ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:46:22Z" - latency: 2.054041ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:45:22Z" - latency: 1.93662ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:44:22Z" - latency: 1.790799ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:43:22Z" - latency: 1.880324ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:42:22Z" - latency: 1.800178ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:41:22Z" - latency: 2.036391ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:40:22Z" - latency: 2.117807ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:39:22Z" - latency: 2.073552ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:38:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:51:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-163-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-163.ec2.internal uid: 208b79d5-d232-43aa-b4fa-877dd32d838b resourceVersion: "41849" uid: 81326dd8-99f9-4211-914f-55e933d43405 spec: sourcePod: network-check-source-8894fc9bd-98fl9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:57:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.065µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:51:22Z" - latency: 1.533654ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:51:22Z" - latency: 887.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:50:22Z" - latency: 1.63095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:50:22Z" - latency: 783.449µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:49:22Z" - latency: 1.508242ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:49:22Z" - latency: 777.852µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:48:22Z" - latency: 1.665702ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:48:22Z" - latency: 937.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:47:22Z" - latency: 1.724652ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:47:22Z" kind: List metadata: resourceVersion: ""