apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "49202" uid: abdff473-bfaf-4c5f-8c8c-0a058e310ae1 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-12T19:34:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.15302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 865.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 1.086619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 814.945µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:45Z" - latency: 1.168777ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:45Z" - latency: 957.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:50:45Z" - latency: 1.148755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:49:45Z" - latency: 941.198µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:48:45Z" - latency: 1.144354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:47:45Z" - latency: 958.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:46:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "51656" uid: c6edffa5-3b6c-4bfd-bd8e-d32ef889a23c spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T19:33:45Z" message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.041383ms message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:45Z" - latency: 8.577626ms message: 'load-balancer-api-external: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:45Z" - latency: 5.60166ms message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:45Z" - latency: 8.390642ms message: 'load-balancer-api-external: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:56:45Z" - latency: 4.81254ms message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 13.597876ms message: 'load-balancer-api-external: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:55:45Z" - latency: 3.851845ms message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 8.340394ms message: 'load-balancer-api-external: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:54:45Z" - latency: 6.446734ms message: 'load-balancer-api-external: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 8.49849ms message: 'load-balancer-api-external: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:53:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "51657" uid: cba7245f-0c5c-49e2-ae47-a4d4a39cf467 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-12T19:33:45Z" message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.753985ms message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:45Z" - latency: 8.456836ms message: 'load-balancer-api-internal: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:45Z" - latency: 5.615571ms message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:45Z" - latency: 8.346962ms message: 'load-balancer-api-internal: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:56:45Z" - latency: 4.791044ms message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 13.521596ms message: 'load-balancer-api-internal: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:55:45Z" - latency: 3.810926ms message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 8.391126ms message: 'load-balancer-api-internal: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:54:45Z" - latency: 6.413383ms message: 'load-balancer-api-internal: tcp connection to aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 8.519049ms message: 'load-balancer-api-internal: resolved host name aab5552473c224dc2b1a52ad4d7da62c-f0c6c2c1fced74ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-12T19:53:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-network-check-target-ip-10-0-129-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "49199" uid: 3b56cba9-2e9e-4fc7-895b-d50b3b801771 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:34:45Z" message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.277711ms message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 1.064003ms message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 801.224µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 886.209µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:45Z" - latency: 978.795µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:45Z" - latency: 1.028078ms message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:50:45Z" - latency: 912.339µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:49:45Z" - latency: 1.299267ms message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:48:45Z" - latency: 962.364µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:47:45Z" - latency: 866.633µs message: 'network-check-target-ip-10-0-129-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:46:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-network-check-target-ip-10-0-130-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "49201" uid: e5317a46-ee34-4654-a3e5-161cab931e84 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:34:45Z" message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.074288ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 2.122831ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 2.253025ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 2.011085ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:45Z" - latency: 2.066216ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:45Z" - latency: 2.357958ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:50:45Z" - latency: 2.022634ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:49:45Z" - latency: 2.350102ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:48:45Z" - latency: 2.370813ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:47:45Z" - latency: 2.38952ms message: 'network-check-target-ip-10-0-130-167: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:46:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-network-check-target-ip-10-0-133-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "49200" uid: 6a7e6694-1630-4351-8d43-caf86f8da553 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-12T19:34:45Z" message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.509245ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 2.072566ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 2.083921ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 1.806602ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:52:45Z" - latency: 2.49248ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:51:45Z" - latency: 2.054945ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:50:45Z" - latency: 1.753093ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:49:45Z" - latency: 1.916115ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:48:45Z" - latency: 1.973487ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:47:45Z" - latency: 1.985978ms message: 'network-check-target-ip-10-0-133-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:46:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-12T19:27:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-169.ec2.internal uid: 80f438b8-b873-4dbf-b018-bea060981791 resourceVersion: "51655" uid: 83991425-6a34-4e69-898b-85f0b31050f5 spec: sourcePod: network-check-source-869dcfcdcd-khb54 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-12T19:33:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 728.63µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:57:45Z" - latency: 2.246231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:57:45Z" - latency: 1.165876ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:56:45Z" - latency: 1.61498ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:56:45Z" - latency: 885.105µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:55:45Z" - latency: 2.663163ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:55:45Z" - latency: 916.688µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:54:45Z" - latency: 1.647876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:54:45Z" - latency: 1.388124ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-12T19:53:45Z" - latency: 1.724538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-12T19:53:45Z" kind: List metadata: resourceVersion: ""