apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "54195" uid: 3fdb3956-a239-4e35-a62d-927801676555 spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T00:13:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 890.2µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 1.369956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 1.126307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 1.202462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:31:54Z" - latency: 1.304055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:30:54Z" - latency: 1.089322ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:29:54Z" - latency: 900.255µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:28:54Z" - latency: 1.084447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:27:54Z" - latency: 985.947µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:26:54Z" - latency: 1.424635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:25:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "55699" uid: 15b7007a-26ed-4936-93f0-086b887d02a7 spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T00:12:54Z" message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.484714ms message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:36:54Z" - latency: 7.181771ms message: 'load-balancer-api-external: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:36:54Z" - latency: 4.275886ms message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:35:54Z" - latency: 7.424567ms message: 'load-balancer-api-external: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:35:54Z" - latency: 4.024912ms message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 7.932893ms message: 'load-balancer-api-external: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:34:54Z" - latency: 9.233231ms message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 7.617115ms message: 'load-balancer-api-external: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:33:54Z" - latency: 5.000334ms message: 'load-balancer-api-external: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 6.553541ms message: 'load-balancer-api-external: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:32:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "55700" uid: 7fbaa25d-4f56-4ef6-ab50-4ac99538fbcd spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T00:12:54Z" message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.423679ms message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:36:54Z" - latency: 7.24234ms message: 'load-balancer-api-internal: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:36:54Z" - latency: 4.307138ms message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:35:54Z" - latency: 7.299284ms message: 'load-balancer-api-internal: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:35:54Z" - latency: 4.073684ms message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 7.8064ms message: 'load-balancer-api-internal: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:34:54Z" - latency: 9.216548ms message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 7.639371ms message: 'load-balancer-api-internal: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:33:54Z" - latency: 4.991873ms message: 'load-balancer-api-internal: tcp connection to a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 6.608032ms message: 'load-balancer-api-internal: resolved host name a1b0b9022dd164acca25c09a9264eb4d-6751a6599af3d208.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T00:32:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-128-150 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "54194" uid: 5d252071-3480-4627-be5b-f5eb8ad22151 spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T00:13:54Z" message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.415079ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 2.403144ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 2.283393ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 2.275625ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:31:54Z" - latency: 2.331743ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:30:54Z" - latency: 2.372792ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:29:54Z" - latency: 2.219063ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:28:54Z" - latency: 2.728048ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:27:54Z" - latency: 2.290917ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:26:54Z" - latency: 2.500865ms message: 'network-check-target-ip-10-0-128-150: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:25:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-135-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "54192" uid: 6e2bd0f8-750c-488b-8ed1-03cbaceb4af7 spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T00:13:54Z" message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088952ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 1.735807ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 1.307511ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 985.925µs message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:31:54Z" - latency: 999.006µs message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:30:54Z" - latency: 1.01434ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:29:54Z" - latency: 859.667µs message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:28:54Z" - latency: 1.01292ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:27:54Z" - latency: 1.190679ms message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:26:54Z" - latency: 723.922µs message: 'network-check-target-ip-10-0-135-226: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:25:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-network-check-target-ip-10-0-136-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "54193" uid: cce3f986-6dcb-4b53-ae3b-5db52b6e0103 spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-08T00:13:54Z" message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.442809ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 2.080604ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 2.638005ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 2.49978ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:31:54Z" - latency: 2.877897ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:30:54Z" - latency: 2.474536ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:29:54Z" - latency: 2.190022ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:28:54Z" - latency: 2.810609ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:27:54Z" - latency: 2.90774ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:26:54Z" - latency: 2.718325ms message: 'network-check-target-ip-10-0-136-92: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:25:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T00:06:53Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-226-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-226.ec2.internal uid: fe591381-6f99-4df7-beb2-0dcc7a034ab2 resourceVersion: "55698" uid: 24b62c35-7fd1-4d03-aa8a-a84483803e2a spec: sourcePod: network-check-source-685456655f-pjbjw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T00:12:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:36:54Z" - latency: 1.938372ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T00:36:54Z" - latency: 933.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:35:54Z" - latency: 2.192167ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T00:35:54Z" - latency: 833.998µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:34:54Z" - latency: 1.584912ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T00:34:54Z" - latency: 815.184µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:33:54Z" - latency: 2.473701ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T00:33:54Z" - latency: 824.36µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T00:32:54Z" - latency: 1.784655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T00:32:54Z" kind: List metadata: resourceVersion: ""