apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61938" uid: df0ee21b-a84f-4cc2-a5f4-5d0302496112 spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-14T23:07:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.473µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 837.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 985.171µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 1.176369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 1.050387ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 1.291952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:37:12Z" - latency: 1.184269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:36:12Z" - latency: 987.401µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:35:12Z" - latency: 872.699µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:34:12Z" - latency: 1.050509ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:33:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61940" uid: 1ab72aa8-7be2-41e7-915f-96ba468e0a9f spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T23:06:12Z" message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.874121ms message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 9.297651ms message: 'load-balancer-api-external: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:42:12Z" - latency: 6.408635ms message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 8.250081ms message: 'load-balancer-api-external: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:41:12Z" - latency: 10.98395ms message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 8.641172ms message: 'load-balancer-api-external: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:40:12Z" - latency: 5.694256ms message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 9.042778ms message: 'load-balancer-api-external: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:39:12Z" - latency: 5.170155ms message: 'load-balancer-api-external: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 8.786844ms message: 'load-balancer-api-external: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61939" uid: 7803f10f-8153-42e1-8181-674972dcacfa spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-14T23:06:12Z" message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.606208ms message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 9.255778ms message: 'load-balancer-api-internal: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:42:12Z" - latency: 5.987847ms message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 8.158054ms message: 'load-balancer-api-internal: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:41:12Z" - latency: 6.335833ms message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 8.590207ms message: 'load-balancer-api-internal: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:40:12Z" - latency: 5.679045ms message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 9.08084ms message: 'load-balancer-api-internal: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:39:12Z" - latency: 4.786031ms message: 'load-balancer-api-internal: tcp connection to a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 8.7343ms message: 'load-balancer-api-internal: resolved host name a8d0ca1b1b05d40dd9f8ec41ec3ca6e0-53a32224a5055139.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-14T23:38:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-130-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61934" uid: a0130b4f-144c-40c6-914a-f4a5cec7a5dc spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T23:07:12Z" message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.545643ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 1.01928ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 1.118559ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 924.187µs message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 951.413µs message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 946.819µs message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:37:12Z" - latency: 1.64899ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:36:12Z" - latency: 1.495782ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:35:12Z" - latency: 1.213809ms message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:34:12Z" - latency: 877.291µs message: 'network-check-target-ip-10-0-130-2: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:33:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-134-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61936" uid: c0df3c23-abaf-4fe5-a208-21fb5b2c5286 spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-14T23:07:12Z" message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.60389ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 2.224495ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 2.372766ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 2.3347ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 2.426429ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 2.504857ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:37:12Z" - latency: 2.49378ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:36:12Z" - latency: 3.19759ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:35:12Z" - latency: 2.360186ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:34:12Z" - latency: 2.384756ms message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:33:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-network-check-target-ip-10-0-136-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61935" uid: bcc1bf00-9a5e-4265-8b0a-48335b1408f4 spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-14T23:07:12Z" message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303701ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 2.183897ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 2.536333ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 2.488844ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 2.339377ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 2.565934ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:37:12Z" - latency: 2.642692ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:36:12Z" - latency: 2.996939ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:35:12Z" - latency: 2.44636ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:34:12Z" - latency: 2.7275ms message: 'network-check-target-ip-10-0-136-11: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:33:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-14T23:00:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-2-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-2.ec2.internal uid: ab7276c8-6965-450c-98f6-7f9a47a5f61b resourceVersion: "61937" uid: a313c634-2f56-4970-a9e4-3560bda70c78 spec: sourcePod: network-check-source-869dcfcdcd-nz8h8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-14T23:06:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.131µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:42:12Z" - latency: 2.364833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T23:42:12Z" - latency: 901.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:41:12Z" - latency: 1.805489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T23:41:12Z" - latency: 977.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:40:12Z" - latency: 1.851108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T23:40:12Z" - latency: 1.230816ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:39:12Z" - latency: 1.903161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T23:39:12Z" - latency: 943.5µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-14T23:38:12Z" - latency: 1.913357ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-14T23:38:12Z" kind: List metadata: resourceVersion: ""