apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "54637" uid: de43adf3-73ae-4abb-a3c8-dd5f2edc547c spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T19:31: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.035186ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 936.308µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 1.200782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 1.267861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:06Z" - latency: 1.109832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:06Z" - latency: 850.581µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:06Z" - latency: 925.269µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:53:06Z" - latency: 982.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:52:06Z" - latency: 894.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:06Z" - latency: 1.074992ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "56599" uid: 1d584a75-7d08-45ad-9316-add603e25376 spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.114972ms message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:06Z" - latency: 7.833553ms message: 'load-balancer-api-external: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:06Z" - latency: 4.355105ms message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:06Z" - latency: 8.361889ms message: 'load-balancer-api-external: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:06Z" - latency: 5.881906ms message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 9.029023ms message: 'load-balancer-api-external: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:59:06Z" - latency: 5.559514ms message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 7.045548ms message: 'load-balancer-api-external: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:58:06Z" - latency: 4.900413ms message: 'load-balancer-api-external: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 8.356692ms message: 'load-balancer-api-external: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:57:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "56598" uid: ce15de5f-6886-47ab-9b33-16fd32643add spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.407862ms message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:06Z" - latency: 7.927802ms message: 'load-balancer-api-internal: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:06Z" - latency: 4.350874ms message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:06Z" - latency: 8.425851ms message: 'load-balancer-api-internal: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:06Z" - latency: 5.906017ms message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 9.083515ms message: 'load-balancer-api-internal: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:59:06Z" - latency: 5.540778ms message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 7.16419ms message: 'load-balancer-api-internal: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:58:06Z" - latency: 4.89634ms message: 'load-balancer-api-internal: tcp connection to a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 8.383033ms message: 'load-balancer-api-internal: resolved host name a8e5f60cb43d34688bcaa27399966a2d-c42927098d644589.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T19:57:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-130-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "54634" uid: 929d6d4a-acf3-4841-a1ec-35eb5f8d5e45 spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 982.038µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 895.185µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 1.175455ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 1.446611ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:06Z" - latency: 921.064µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:06Z" - latency: 1.265006ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:06Z" - latency: 921.652µs message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:53:06Z" - latency: 1.198182ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:52:06Z" - latency: 1.259766ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:06Z" - latency: 1.108877ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-131-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "54635" uid: 809cc233-9c26-4e3e-9e0b-b305c45151ad spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.169302ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 2.127497ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 2.24122ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 2.899382ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:06Z" - latency: 2.121047ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:06Z" - latency: 2.196738ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:06Z" - latency: 2.044219ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:53:06Z" - latency: 2.137148ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:52:06Z" - latency: 2.300564ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:06Z" - latency: 2.414197ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-ip-10-0-135-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "54636" uid: d1aea720-c947-4aff-90a3-25bc7219c27d spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.464583ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 1.94889ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 2.065693ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 2.460651ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:56:06Z" - latency: 2.058929ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:55:06Z" - latency: 2.182167ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:54:06Z" - latency: 2.15301ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:53:06Z" - latency: 2.015852ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:52:06Z" - latency: 2.312128ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:51:06Z" - latency: 2.276061ms message: 'network-check-target-ip-10-0-135-109: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:50:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T19:24:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-239-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-239.ec2.internal uid: ef0ddf8e-8bae-45f5-b919-25bb1b7216c7 resourceVersion: "56597" uid: 66504e72-89a8-47e6-8616-1e4af29ee3a4 spec: sourcePod: network-check-source-989f8b8dc-vf6t5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T19:31:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.074412ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:01:06Z" - latency: 1.621561ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:01:06Z" - latency: 1.17556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T20:00:06Z" - latency: 1.983172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T20:00:06Z" - latency: 847.205µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:59:06Z" - latency: 1.767608ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:59:06Z" - latency: 1.051112ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:58:06Z" - latency: 1.809007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:58:06Z" - latency: 1.306926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T19:57:06Z" - latency: 1.790285ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T19:57:06Z" kind: List metadata: resourceVersion: ""