apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "20784" uid: 62a19f67-04c5-4492-84e5-709ad5535692 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T11:34:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.125106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 1.747889ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 1.073367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:46:06Z" - latency: 1.22697ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:45:06Z" - latency: 1.037802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:44:06Z" - latency: 1.007676ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:43:06Z" - latency: 1.124405ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:42:06Z" - latency: 1.105913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:41:06Z" - latency: 1.148231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:40:06Z" - latency: 954.751µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "22208" uid: b8152bf5-7ec6-49d6-a0a2-371300a14966 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T11:33:06Z" message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.978486ms message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:51:06Z" - latency: 6.659334ms message: 'load-balancer-api-external: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:51:06Z" - latency: 4.488639ms message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:50:06Z" - latency: 6.566323ms message: 'load-balancer-api-external: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:50:06Z" - latency: 6.128218ms message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:49:06Z" - latency: 7.515435ms message: 'load-balancer-api-external: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:49:06Z" - latency: 6.341285ms message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 6.702447ms message: 'load-balancer-api-external: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:48:06Z" - latency: 6.247471ms message: 'load-balancer-api-external: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 7.127967ms message: 'load-balancer-api-external: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "22207" uid: 911a8719-89bc-4d91-9305-985d38676ea4 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T11:33:06Z" message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.524744ms message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:51:06Z" - latency: 6.734986ms message: 'load-balancer-api-internal: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:51:06Z" - latency: 4.525124ms message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:50:06Z" - latency: 6.507944ms message: 'load-balancer-api-internal: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:50:06Z" - latency: 6.125935ms message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:49:06Z" - latency: 7.597662ms message: 'load-balancer-api-internal: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:49:06Z" - latency: 6.269125ms message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 6.731483ms message: 'load-balancer-api-internal: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:48:06Z" - latency: 5.328104ms message: 'load-balancer-api-internal: tcp connection to acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 7.158163ms message: 'load-balancer-api-internal: resolved host name acdb0bad3b6124e1584d4d909768f912-f4171209f15a26aa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T11:47:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-130-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "20781" uid: bceb3c01-666f-43da-9547-ca7fd716e953 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:34:06Z" message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 741.733µs message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 1.451644ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 853.197µs message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:46:06Z" - latency: 1.015051ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:45:06Z" - latency: 890.509µs message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:44:06Z" - latency: 920.935µs message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:43:06Z" - latency: 1.061173ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:42:06Z" - latency: 1.417315ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:41:06Z" - latency: 1.191993ms message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:40:06Z" - latency: 804.338µs message: 'network-check-target-ip-10-0-130-94: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "20782" uid: 12eb1d55-7418-4a41-83a2-94e577ce1752 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:34:06Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.730882ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 1.529871ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 1.836948ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:46:06Z" - latency: 1.945922ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:45:06Z" - latency: 1.81746ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:44:06Z" - latency: 1.632804ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:43:06Z" - latency: 2.044898ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:42:06Z" - latency: 2.223592ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:41:06Z" - latency: 1.918432ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:40:06Z" - latency: 1.622618ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-ip-10-0-141-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "20783" uid: b00718b2-dfa0-4801-b315-510542a49fc2 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-08T11:34:06Z" message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.143186ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 2.432406ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 1.892308ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:46:06Z" - latency: 2.324599ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:45:06Z" - latency: 2.205003ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:44:06Z" - latency: 2.015966ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:43:06Z" - latency: 2.326172ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:42:06Z" - latency: 2.317124ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:41:06Z" - latency: 2.134904ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:40:06Z" - latency: 2.086634ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T11:27:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-94-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-94.ec2.internal uid: c5cb3030-3ab5-4552-97d0-055d798ae825 resourceVersion: "22206" uid: d03768d8-73d7-4b47-8799-355aadfbac21 spec: sourcePod: network-check-source-dbd9cf844-47jkz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T11:33:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.995µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:51:06Z" - latency: 1.81263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T11:51:06Z" - latency: 985.838µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:50:06Z" - latency: 1.789222ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T11:50:06Z" - latency: 1.028407ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:49:06Z" - latency: 2.060414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T11:49:06Z" - latency: 1.013983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:48:06Z" - latency: 1.832239ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T11:48:06Z" - latency: 779.183µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T11:47:06Z" - latency: 2.555341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T11:47:06Z" kind: List metadata: resourceVersion: ""