apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "53371" uid: c6e50deb-29a9-4908-9e4a-3a4437d32d5d spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T15:05:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 983.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 1.073864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 860.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 1.004462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:23:28Z" - latency: 1.087609ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:22:28Z" - latency: 999.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:21:28Z" - latency: 1.084069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:20:28Z" - latency: 1.265985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:19:28Z" - latency: 1.038524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:18:28Z" - latency: 1.230416ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:17:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "54967" uid: 11e24fe5-2d56-4b55-ac39-25a184f5335d spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T15:04:28Z" message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.599118ms message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:28:28Z" - latency: 6.915022ms message: 'load-balancer-api-external: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:28:28Z" - latency: 3.582357ms message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:27:28Z" - latency: 7.00661ms message: 'load-balancer-api-external: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:27:28Z" - latency: 3.437143ms message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 7.036012ms message: 'load-balancer-api-external: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:26:28Z" - latency: 4.857617ms message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 6.760747ms message: 'load-balancer-api-external: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:25:28Z" - latency: 5.450826ms message: 'load-balancer-api-external: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 6.662024ms message: 'load-balancer-api-external: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:24:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "54966" uid: 9a82cfed-af0b-4810-a689-f7c241a0afa8 spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T15:04:28Z" message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.909261ms message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:28:28Z" - latency: 6.954739ms message: 'load-balancer-api-internal: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:28:28Z" - latency: 3.703406ms message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:27:28Z" - latency: 6.989528ms message: 'load-balancer-api-internal: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:27:28Z" - latency: 5.346397ms message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 6.954499ms message: 'load-balancer-api-internal: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:26:28Z" - latency: 4.857021ms message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 6.632424ms message: 'load-balancer-api-internal: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:25:28Z" - latency: 5.424213ms message: 'load-balancer-api-internal: tcp connection to a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 6.678887ms message: 'load-balancer-api-internal: resolved host name a79372c6189fc406d9677d01fd3ef925-a16dabaa96d3bef9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T15:24:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-134-147 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "53368" uid: a50b9180-ad13-40a4-a2e1-2156ba055a47 spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:05:28Z" message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 915.333µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 1.149552ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 994.495µs message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 1.162803ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:23:28Z" - latency: 1.844977ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:22:28Z" - latency: 1.128409ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:21:28Z" - latency: 1.208736ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:20:28Z" - latency: 1.084716ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:19:28Z" - latency: 1.076903ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:18:28Z" - latency: 1.084252ms message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:17:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-136-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "53369" uid: 4822f5f3-af88-42d0-bc1a-8f2276cb6b91 spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:05:28Z" message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.212027ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 2.517831ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 2.448002ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 2.331615ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:23:28Z" - latency: 3.027042ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:22:28Z" - latency: 2.555816ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:21:28Z" - latency: 2.630668ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:20:28Z" - latency: 2.421904ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:19:28Z" - latency: 2.60416ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:18:28Z" - latency: 2.273254ms message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:17:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-ip-10-0-137-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "53370" uid: bbcda334-f66f-4150-b7e5-0263cc3ac5b4 spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T15:05:28Z" message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.58036ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 2.470501ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 2.469425ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 1.916329ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:23:28Z" - latency: 2.562471ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:22:28Z" - latency: 2.334407ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:21:28Z" - latency: 2.175616ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:20:28Z" - latency: 2.229606ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:19:28Z" - latency: 2.696598ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:18:28Z" - latency: 2.207337ms message: 'network-check-target-ip-10-0-137-101: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:17:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T14:58:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-147-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-147.ec2.internal uid: 00c6e731-6771-438f-8f8d-988fb58e6b3f resourceVersion: "54964" uid: f2b5f36c-df5c-4c27-94f6-bf9787b0c5c7 spec: sourcePod: network-check-source-685456655f-j96p5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T15:04:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.096749ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:28:28Z" - latency: 2.102866ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:28:28Z" - latency: 1.023542ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:27:28Z" - latency: 2.372902ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:27:28Z" - latency: 1.213444ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:26:28Z" - latency: 1.647144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:26:28Z" - latency: 887.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:25:28Z" - latency: 1.796379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:25:28Z" - latency: 1.214369ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T15:24:28Z" - latency: 1.855778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T15:24:28Z" kind: List metadata: resourceVersion: ""