apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "52761" uid: 75a23c75-2d49-4bf7-a77b-639b5fdc8376 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T13:40:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.137786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 1.032024ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 1.145993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 958.469µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 915.183µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:04:50Z" - latency: 918.194µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:03:50Z" - latency: 794.129µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:02:50Z" - latency: 994.331µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:01:50Z" - latency: 1.168373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:00:50Z" - latency: 1.418504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:59:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "54018" uid: ff91cc6f-cb36-4e9f-82bd-44ff05ea0c26 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:39:50Z" message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.765232ms message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:09:50Z" - latency: 7.284196ms message: 'load-balancer-api-external: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:09:50Z" - latency: 4.877684ms message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 6.294215ms message: 'load-balancer-api-external: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:08:50Z" - latency: 3.805879ms message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 6.892101ms message: 'load-balancer-api-external: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:07:50Z" - latency: 4.069522ms message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 6.406889ms message: 'load-balancer-api-external: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:06:50Z" - latency: 4.845682ms message: 'load-balancer-api-external: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 7.305738ms message: 'load-balancer-api-external: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:05:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "54019" uid: 601f4d39-4287-467c-82bf-fb2f6c6aa100 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:39:50Z" message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.629423ms message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:09:50Z" - latency: 7.36823ms message: 'load-balancer-api-internal: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:09:50Z" - latency: 4.806824ms message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 6.426142ms message: 'load-balancer-api-internal: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:08:50Z" - latency: 4.131328ms message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 7.013138ms message: 'load-balancer-api-internal: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:07:50Z" - latency: 3.845244ms message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 6.488461ms message: 'load-balancer-api-internal: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:06:50Z" - latency: 3.610938ms message: 'load-balancer-api-internal: tcp connection to a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 7.404006ms message: 'load-balancer-api-internal: resolved host name a510c19355abc4132ba77d32614b221e-11c3e079cc60eabf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T14:05:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-network-check-target-ip-10-0-138-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "52758" uid: 00dd3ae3-87c3-465a-b3ae-fde091922b07 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:40:50Z" message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.334557ms message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 885.628µs message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 1.135396ms message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 1.05599ms message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 769.715µs message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:04:50Z" - latency: 1.057028ms message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:03:50Z" - latency: 981.78µs message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:02:50Z" - latency: 866.168µs message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:01:50Z" - latency: 1.81032ms message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:00:50Z" - latency: 829.109µs message: 'network-check-target-ip-10-0-138-68: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:59:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-network-check-target-ip-10-0-139-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "52759" uid: 626149bf-70fd-42a3-a81e-632dca102978 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:40:50Z" message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.162541ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 2.180954ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 2.203341ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 2.063471ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 2.129075ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:04:50Z" - latency: 2.067528ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:03:50Z" - latency: 2.159603ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:02:50Z" - latency: 2.221573ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:01:50Z" - latency: 2.271776ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:00:50Z" - latency: 2.533688ms message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:59:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-network-check-target-ip-10-0-142-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "52760" uid: f9deefb3-6dcf-449a-bbf2-aebb731476e5 spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:40:50Z" message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.983564ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 1.926403ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 2.021685ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 1.684183ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 1.55082ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:04:50Z" - latency: 1.995126ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:03:50Z" - latency: 1.868731ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:02:50Z" - latency: 2.071853ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:01:50Z" - latency: 2.236325ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:00:50Z" - latency: 1.691173ms message: 'network-check-target-ip-10-0-142-213: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:59:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:33:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-68-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-68.ec2.internal uid: 3b9bc14b-177c-424e-90c0-2e4ed0fc8ed5 resourceVersion: "54017" uid: 7d19a9bf-b4e2-4aea-bd32-4be1f9b1314d spec: sourcePod: network-check-source-dbd9cf844-hr5dx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T13:39:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.1804ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:09:50Z" - latency: 1.843112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:09:50Z" - latency: 1.16653ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:08:50Z" - latency: 1.845083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:08:50Z" - latency: 835.145µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:07:50Z" - latency: 1.954416ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:07:50Z" - latency: 900.534µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:06:50Z" - latency: 2.071897ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:06:50Z" - latency: 890.936µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T14:05:50Z" - latency: 2.059328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T14:05:50Z" kind: List metadata: resourceVersion: ""