apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "39002" uid: c4dcdc82-07bb-4e29-8b9e-6b8e85034ab7 spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T21:02:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 978.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:44:05Z" - latency: 1.257641ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 931.189µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 1.021757ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 1.01256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 1.023891ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 1.148711ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:38:05Z" - latency: 920.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:37:05Z" - latency: 1.11542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:36:05Z" - latency: 961.651µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "38531" uid: 6c4c1cee-1141-4d3c-a720-2e9135585df2 spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T21:01:05Z" message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.152885ms message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 8.129489ms message: 'load-balancer-api-external: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:43:05Z" - latency: 5.573386ms message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 11.029142ms message: 'load-balancer-api-external: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:42:05Z" - latency: 4.937933ms message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 9.669208ms message: 'load-balancer-api-external: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:41:05Z" - latency: 4.126772ms message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 8.768327ms message: 'load-balancer-api-external: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:40:05Z" - latency: 5.154015ms message: 'load-balancer-api-external: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 9.316839ms message: 'load-balancer-api-external: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "38532" uid: 37fe2d54-d7ae-4884-af41-e66f5b743bfa spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T21:01:05Z" message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.12388ms message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 8.257215ms message: 'load-balancer-api-internal: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:43:05Z" - latency: 5.595616ms message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 10.940912ms message: 'load-balancer-api-internal: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:42:05Z" - latency: 4.969132ms message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 9.61163ms message: 'load-balancer-api-internal: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:41:05Z" - latency: 4.660998ms message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 8.662102ms message: 'load-balancer-api-internal: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:40:05Z" - latency: 5.19269ms message: 'load-balancer-api-internal: tcp connection to a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 9.266116ms message: 'load-balancer-api-internal: resolved host name a5257fa2312304d37bb73130220e2a0f-3c762382b5e59090.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T21:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-130-40 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "38999" uid: 1f0a4b7c-b4d2-4f02-8b9e-6c012faa5e50 spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:05Z" message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.109µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:44:05Z" - latency: 1.153252ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 1.3258ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 1.052474ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 916.555µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 881.095µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 1.312179ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:38:05Z" - latency: 1.2391ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:37:05Z" - latency: 1.274783ms message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:36:05Z" - latency: 897.511µs message: 'network-check-target-ip-10-0-130-40: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-136-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "39001" uid: b69454d6-b8a1-4fd7-ab07-2e36cc4895ee spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:05Z" message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.403315ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:44:05Z" - latency: 2.592847ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 2.585339ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 2.194602ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 2.02356ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 1.947805ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 2.341029ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:38:05Z" - latency: 2.164805ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:37:05Z" - latency: 2.39485ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:36:05Z" - latency: 2.263244ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-ip-10-0-137-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "39000" uid: a45f27c2-cef9-4f73-9d34-c5ddfe12fa2f spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-09T21:02:05Z" message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.343927ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:44:05Z" - latency: 2.288583ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 2.171254ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 2.234222ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 2.069027ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 2.171833ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 2.312318ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:38:05Z" - latency: 2.315587ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:37:05Z" - latency: 2.358449ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:36:05Z" - latency: 1.913847ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:35:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T20:55:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-40-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-40.ec2.internal uid: fe2ab1db-5889-45e3-8649-a1f0fe1958d7 resourceVersion: "38530" uid: 16343a4f-aa73-429e-a793-2297a74f79df spec: sourcePod: network-check-source-685456655f-qd7jf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T21:01:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214762ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:43:05Z" - latency: 1.610825ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:43:05Z" - latency: 875.059µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:42:05Z" - latency: 2.629457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:42:05Z" - latency: 1.00946ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:41:05Z" - latency: 1.695795ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:41:05Z" - latency: 908.831µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:40:05Z" - latency: 2.470383ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:40:05Z" - latency: 1.252325ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T21:39:05Z" - latency: 1.712007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T21:39:05Z" kind: List metadata: resourceVersion: ""