apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "18664" uid: d06141f6-6ec1-48e4-8b33-1443b52be684 spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T13:43:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.528µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 1.065404ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:49:13Z" - latency: 844.517µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:48:13Z" - latency: 787.829µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:47:13Z" - latency: 790.511µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:46:13Z" - latency: 768.446µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:45:13Z" - latency: 1.196537ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:44:13Z" - latency: 790.102µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:43:13Z" - latency: 830.154µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:42:13Z" - latency: 1.05089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "20718" uid: 5c8a9866-1f48-4956-8c69-20b6d649c35d spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T13:42:13Z" message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.526265ms message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:54:13Z" - latency: 8.621669ms message: 'load-balancer-api-external: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:54:13Z" - latency: 5.154786ms message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:53:13Z" - latency: 9.316303ms message: 'load-balancer-api-external: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:53:13Z" - latency: 4.399006ms message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:52:13Z" - latency: 6.686459ms message: 'load-balancer-api-external: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:52:13Z" - latency: 4.560503ms message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:51:13Z" - latency: 7.223607ms message: 'load-balancer-api-external: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:51:13Z" - latency: 5.132356ms message: 'load-balancer-api-external: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 7.872237ms message: 'load-balancer-api-external: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "20717" uid: 1f5b8336-c875-425c-8c0a-25252e3e917a spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T13:42:13Z" message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.748779ms message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:54:13Z" - latency: 8.706974ms message: 'load-balancer-api-internal: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:54:13Z" - latency: 4.687691ms message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:53:13Z" - latency: 9.432149ms message: 'load-balancer-api-internal: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:53:13Z" - latency: 4.58683ms message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:52:13Z" - latency: 6.714523ms message: 'load-balancer-api-internal: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:52:13Z" - latency: 3.981667ms message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:51:13Z" - latency: 7.434397ms message: 'load-balancer-api-internal: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:51:13Z" - latency: 5.16228ms message: 'load-balancer-api-internal: tcp connection to a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 7.8938ms message: 'load-balancer-api-internal: resolved host name a4e3dac1b6ee94fb98801e9771684641-20376645b0611f23.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T13:50:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-network-check-target-ip-10-0-129-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "18661" uid: 4b83c70b-90f0-4bfb-abc6-21561e055823 spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:43:13Z" message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 753.727µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 927.523µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:49:13Z" - latency: 916.272µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:48:13Z" - latency: 794.974µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:47:13Z" - latency: 1.103593ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:46:13Z" - latency: 1.065408ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:45:13Z" - latency: 919.923µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:44:13Z" - latency: 1.093433ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:43:13Z" - latency: 825.332µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:42:13Z" - latency: 807.864µs message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-network-check-target-ip-10-0-134-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "18663" uid: 2a4e07cf-afeb-451c-aee5-95f137cddc31 spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:43:13Z" message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.249944ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 2.430101ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:49:13Z" - latency: 2.115577ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:48:13Z" - latency: 1.952087ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:47:13Z" - latency: 2.083009ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:46:13Z" - latency: 2.021832ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:45:13Z" - latency: 2.263199ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:44:13Z" - latency: 2.023517ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:43:13Z" - latency: 2.008439ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:42:13Z" - latency: 1.993183ms message: 'network-check-target-ip-10-0-134-22: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-network-check-target-ip-10-0-136-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "18662" uid: c12f0980-9d38-4e27-886d-c1d34741957c spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T13:43:13Z" message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323611ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 2.237158ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:49:13Z" - latency: 2.159811ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:48:13Z" - latency: 2.224863ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:47:13Z" - latency: 2.022028ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:46:13Z" - latency: 2.194227ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:45:13Z" - latency: 2.114959ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:44:13Z" - latency: 2.293718ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:43:13Z" - latency: 2.67328ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:42:13Z" - latency: 2.204161ms message: 'network-check-target-ip-10-0-136-158: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:41:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T13:36:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-103.ec2.internal uid: fe477e5a-7dea-4d73-99a9-9f23db25e087 resourceVersion: "20716" uid: d782fc4d-d56a-42df-991d-306b49037c52 spec: sourcePod: network-check-source-8894fc9bd-lwwp4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T13:42:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:54:13Z" - latency: 1.599807ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T13:54:13Z" - latency: 1.223944ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:53:13Z" - latency: 1.671584ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T13:53:13Z" - latency: 919.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:52:13Z" - latency: 1.747355ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T13:52:13Z" - latency: 963.333µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:51:13Z" - latency: 1.452217ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T13:51:13Z" - latency: 753.355µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T13:50:13Z" - latency: 1.676012ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T13:50:13Z" kind: List metadata: resourceVersion: ""