apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "22520" uid: 777b1c8e-e80d-4825-8c22-a1f7f288ae5c spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T13:54:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.355µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:15:31Z" - latency: 869.645µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:14:31Z" - latency: 903.167µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:13:31Z" - latency: 1.698589ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:12:31Z" - latency: 922.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 871.142µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 1.373057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 1.414773ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 1.183139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 836.697µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "20726" uid: 24b49763-c8c2-4879-9aaa-eca90b595130 spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T13:53:31Z" message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.824051ms message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 8.591169ms message: 'load-balancer-api-external: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:11:31Z" - latency: 4.015516ms message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 7.958944ms message: 'load-balancer-api-external: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:10:31Z" - latency: 5.182609ms message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 9.837791ms message: 'load-balancer-api-external: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:09:31Z" - latency: 4.412418ms message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 8.915948ms message: 'load-balancer-api-external: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:08:31Z" - latency: 6.341094ms message: 'load-balancer-api-external: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 8.496543ms message: 'load-balancer-api-external: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:07:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "20725" uid: a81cdfb2-54aa-439b-b5f9-d8f74c1dd2df spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T13:53:31Z" message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.933591ms message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 8.485231ms message: 'load-balancer-api-internal: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:11:31Z" - latency: 4.002089ms message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 8.088747ms message: 'load-balancer-api-internal: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:10:31Z" - latency: 5.217772ms message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 9.863944ms message: 'load-balancer-api-internal: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:09:31Z" - latency: 5.286634ms message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 9.042985ms message: 'load-balancer-api-internal: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:08:31Z" - latency: 5.716756ms message: 'load-balancer-api-internal: tcp connection to ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 8.547129ms message: 'load-balancer-api-internal: resolved host name ab7229cfb4e5a4cb79ee89a33ecf6e14-f28938cf234ca301.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T14:07:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-network-check-target-ip-10-0-130-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "22521" uid: c6c116bb-80f6-49bd-9a65-473f44e7600b spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:54:31Z" message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.96173ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:15:31Z" - latency: 2.304337ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:14:31Z" - latency: 2.346548ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:13:31Z" - latency: 2.480665ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:12:31Z" - latency: 2.608078ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 2.1629ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 2.635173ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 2.358948ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 2.154332ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 1.964282ms message: 'network-check-target-ip-10-0-130-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-network-check-target-ip-10-0-131-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "22518" uid: 3484f5ba-3589-4cab-afd8-14e300cb17ed spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:54:31Z" message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.239625ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:15:31Z" - latency: 1.920686ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:14:31Z" - latency: 2.301654ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:13:31Z" - latency: 2.47287ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:12:31Z" - latency: 2.18737ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 2.413661ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 2.071909ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 2.196366ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 2.609231ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 2.124171ms message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-network-check-target-ip-10-0-136-179 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "22519" uid: d27d7ac6-a61f-4644-ad6c-738051bc2a5a spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T13:54:31Z" message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.300136ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:15:31Z" - latency: 862.103µs message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:14:31Z" - latency: 937.778µs message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:13:31Z" - latency: 877.176µs message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:12:31Z" - latency: 834.063µs message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 1.273944ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 1.743023ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 1.626346ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 1.490886ms message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 800.672µs message: 'network-check-target-ip-10-0-136-179: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:06:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T13:47:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-179-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-179.ec2.internal uid: fd82c22d-b04e-4446-9ccb-36f3840bf988 resourceVersion: "20724" uid: fce75031-b426-4444-85d2-5fdab6fd4c00 spec: sourcePod: network-check-source-7d88cb55d8-6pg7g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T13:53:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 942.82µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:11:31Z" - latency: 1.798019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T14:11:31Z" - latency: 1.388365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:10:31Z" - latency: 1.744554ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T14:10:31Z" - latency: 774.604µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:09:31Z" - latency: 2.145039ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T14:09:31Z" - latency: 746.867µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:08:31Z" - latency: 2.401217ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T14:08:31Z" - latency: 975.151µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T14:07:31Z" - latency: 2.207842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T14:07:31Z" kind: List metadata: resourceVersion: ""