apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "23719" uid: 48385ec5-8ce6-4ea4-af4a-6fdb97db31e7 spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T02:01:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.944µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:01:18Z" - latency: 965.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 1.320405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 1.298496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 916.136µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 950.074µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 746.839µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:55:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "22647" uid: e65e6b88-ad14-4269-b122-ab628e610f9e spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T02:00:18Z" message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.600494ms message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 14.529623ms message: 'load-balancer-api-external: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T02:00:18Z" - latency: 4.639696ms message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 7.020651ms message: 'load-balancer-api-external: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:59:18Z" - latency: 3.922958ms message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 6.849606ms message: 'load-balancer-api-external: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:58:18Z" - latency: 4.763843ms message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 7.657268ms message: 'load-balancer-api-external: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:57:18Z" - latency: 4.860853ms message: 'load-balancer-api-external: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 6.518415ms message: 'load-balancer-api-external: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "22648" uid: 38ef7948-001b-4f84-b869-5bc6a3180043 spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T02:00:18Z" message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.296669ms message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 14.714027ms message: 'load-balancer-api-internal: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T02:00:18Z" - latency: 4.64937ms message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 7.149439ms message: 'load-balancer-api-internal: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:59:18Z" - latency: 4.535646ms message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 6.811597ms message: 'load-balancer-api-internal: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:58:18Z" - latency: 4.759088ms message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 7.634627ms message: 'load-balancer-api-internal: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:57:18Z" - latency: 4.657137ms message: 'load-balancer-api-internal: tcp connection to a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 6.472803ms message: 'load-balancer-api-internal: resolved host name a092ea302a6594b299eb495dbbe393d1-3e73d5812f0b332e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T01:56:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-129-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "23717" uid: de58a3d6-ca75-4d24-afe1-dfe7d214c09d spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T02:01:18Z" message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.939506ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:01:18Z" - latency: 3.362206ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 2.210254ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 2.515912ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 2.352258ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 1.947969ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 2.114098ms message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:55:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-129-52 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "23718" uid: 1dbe020f-dacf-417e-aa3e-0bd8322bd265 spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T02:01:18Z" message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.37647ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:01:18Z" - latency: 3.114457ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 2.513177ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 2.092659ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 2.227818ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 2.192906ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 2.779355ms message: 'network-check-target-ip-10-0-129-52: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:55:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-ip-10-0-141-35 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "23716" uid: 4d8e7a20-5cc1-442a-964b-d81a4e3d3a76 spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T02:01:18Z" message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.005673ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:01:18Z" - latency: 1.534616ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 1.491666ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 1.430748ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 1.27403ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 1.206227ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 1.200007ms message: 'network-check-target-ip-10-0-141-35: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:55:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T01:54:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-35-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-35.ec2.internal uid: f4aafd66-11d9-44dd-a6be-be8f2319550b resourceVersion: "22646" uid: 6ae1a6fe-a98e-4a8d-bf58-dde2ce5645c7 spec: sourcePod: network-check-source-8894fc9bd-l6sfq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T02:00:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.034034ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T02:00:18Z" - latency: 3.375515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T02:00:18Z" - latency: 897.021µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:59:18Z" - latency: 1.877832ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T01:59:18Z" - latency: 1.305556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:58:18Z" - latency: 1.769846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T01:58:18Z" - latency: 882.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:57:18Z" - latency: 1.847029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T01:57:18Z" - latency: 960.136µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T01:56:18Z" - latency: 1.646418ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T01:56:18Z" kind: List metadata: resourceVersion: ""