apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "69529" uid: ed4546e5-981b-497e-8d91-a09f0e260ff3 spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T19:44:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 918.042µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 1.330706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 1.135042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 992.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 967.953µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:08:21Z" - latency: 1.098279ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:07:21Z" - latency: 1.017803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:06:21Z" - latency: 1.009235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:05:21Z" - latency: 1.090335ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:04:21Z" - latency: 1.037883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:03:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "70492" uid: da3a6573-5eb8-4478-a6eb-02d6382306bd spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T19:43:21Z" message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.306677ms message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:13:21Z" - latency: 6.344877ms message: 'load-balancer-api-external: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:13:21Z" - latency: 6.278925ms message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 7.770484ms message: 'load-balancer-api-external: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:12:21Z" - latency: 3.448347ms message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 6.729247ms message: 'load-balancer-api-external: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:11:21Z" - latency: 3.76385ms message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 6.899504ms message: 'load-balancer-api-external: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:10:21Z" - latency: 4.227006ms message: 'load-balancer-api-external: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 7.82634ms message: 'load-balancer-api-external: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "70493" uid: 2b7b8d34-82f0-4504-bbda-5a6a139c66a6 spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T19:43:21Z" message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.303323ms message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:13:21Z" - latency: 6.390083ms message: 'load-balancer-api-internal: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:13:21Z" - latency: 6.276235ms message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 7.668989ms message: 'load-balancer-api-internal: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:12:21Z" - latency: 3.445884ms message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 6.676107ms message: 'load-balancer-api-internal: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:11:21Z" - latency: 4.008321ms message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 6.933107ms message: 'load-balancer-api-internal: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:10:21Z" - latency: 4.038153ms message: 'load-balancer-api-internal: tcp connection to af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 7.777396ms message: 'load-balancer-api-internal: resolved host name af56d428111af48ccac855fff79e718d-863c02c859935246.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T20:09:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-136-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "69528" uid: c8ab8a5f-437d-4c55-a653-dc8de0a42603 spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-11T19:44:21Z" message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.221445ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 2.954538ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 2.418276ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 2.403313ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 2.467894ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:08:21Z" - latency: 2.739562ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:07:21Z" - latency: 2.455269ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:06:21Z" - latency: 2.453809ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:05:21Z" - latency: 2.971934ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:04:21Z" - latency: 2.917886ms message: 'network-check-target-ip-10-0-136-27: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:03:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-138-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "69526" uid: 3c3b52eb-840f-4a33-acd8-4e504ef755fe spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T19:44:21Z" message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.314µs message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 1.021252ms message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 930.066µs message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 908.62µs message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 1.527871ms message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:08:21Z" - latency: 1.091203ms message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:07:21Z" - latency: 1.206633ms message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:06:21Z" - latency: 1.196412ms message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:05:21Z" - latency: 953.82µs message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:04:21Z" - latency: 995.009µs message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:03:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-139-38 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "69527" uid: da5d6fd4-6b1b-4dad-8926-dd75336aea01 spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T19:44:21Z" message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.967379ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 2.343921ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 2.700294ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 2.086934ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 2.110439ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:08:21Z" - latency: 2.803757ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:07:21Z" - latency: 2.489694ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:06:21Z" - latency: 2.332322ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:05:21Z" - latency: 2.512252ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:04:21Z" - latency: 2.770693ms message: 'network-check-target-ip-10-0-139-38: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:03:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T19:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-82-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-82.ec2.internal uid: 872d560c-8d91-449f-b143-41916599c2c9 resourceVersion: "70491" uid: 2a97c0a5-7d6e-47aa-94ee-dfb5f83dd3b2 spec: sourcePod: network-check-source-6f8b768455-dm9xm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T19:43:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 931.932µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:13:21Z" - latency: 1.951581ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T20:13:21Z" - latency: 980.183µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:12:21Z" - latency: 2.129605ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T20:12:21Z" - latency: 1.411713ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:11:21Z" - latency: 1.707504ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T20:11:21Z" - latency: 1.545932ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:10:21Z" - latency: 1.826083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T20:10:21Z" - latency: 1.051641ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T20:09:21Z" - latency: 1.830227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T20:09:21Z" kind: List metadata: resourceVersion: ""