apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61521" uid: 8410ce36-cc79-49c1-82bc-486dbf6c4e66 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T22:26:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.075396ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 1.743727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 1.216353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 1.629238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 1.347953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 959.351µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:56:22Z" - latency: 1.588175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:55:22Z" - latency: 1.192495ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:54:22Z" - latency: 1.424725ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:53:22Z" - latency: 1.189277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:52:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61523" uid: 40bc3a5e-887d-4a4f-b43b-b7cf4e034807 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T22:25:22Z" message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.388089ms message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 8.26245ms message: 'load-balancer-api-external: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T23:01:22Z" - latency: 4.887162ms message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 6.881863ms message: 'load-balancer-api-external: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T23:00:22Z" - latency: 5.051845ms message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 7.234739ms message: 'load-balancer-api-external: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:59:22Z" - latency: 5.239926ms message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 8.456154ms message: 'load-balancer-api-external: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:58:22Z" - latency: 4.9135ms message: 'load-balancer-api-external: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 10.87486ms message: 'load-balancer-api-external: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61525" uid: adc19619-4768-4228-a601-4c56f6f69630 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T22:25:22Z" message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.373668ms message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 8.200334ms message: 'load-balancer-api-internal: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T23:01:22Z" - latency: 4.829383ms message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 6.977803ms message: 'load-balancer-api-internal: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T23:00:22Z" - latency: 5.034872ms message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 7.192115ms message: 'load-balancer-api-internal: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:59:22Z" - latency: 5.443719ms message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 8.572574ms message: 'load-balancer-api-internal: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:58:22Z" - latency: 5.803323ms message: 'load-balancer-api-internal: tcp connection to aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 10.82789ms message: 'load-balancer-api-internal: resolved host name aff8f7fda41514f13aeb98e034928934-cbd741e631392276.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T22:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-network-check-target-ip-10-0-136-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61516" uid: 83a5eab5-b208-4f1f-8833-b68a730aace4 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T22:26:22Z" message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014384ms message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 893.672µs message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 912.227µs message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 974.379µs message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 1.478899ms message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 936.758µs message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:56:22Z" - latency: 1.154133ms message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:55:22Z" - latency: 1.438097ms message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:54:22Z" - latency: 858.226µs message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:53:22Z" - latency: 1.110703ms message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:52:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-network-check-target-ip-10-0-136-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61517" uid: 4a3b2f80-b386-4acf-824c-e8c053c6ad54 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T22:26:22Z" message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.987351ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 2.289699ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 1.899072ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 2.389125ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 2.289357ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 2.235748ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:56:22Z" - latency: 2.13292ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:55:22Z" - latency: 2.28115ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:54:22Z" - latency: 2.399165ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:53:22Z" - latency: 2.487205ms message: 'network-check-target-ip-10-0-136-87: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:52:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-network-check-target-ip-10-0-139-92 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61519" uid: 00943f09-2294-4806-a20d-14ec3fd66a1c spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T22:26:22Z" message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312176ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 1.902417ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 2.026026ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 2.142421ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 2.327504ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 2.166361ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:56:22Z" - latency: 2.063312ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:55:22Z" - latency: 2.278202ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:54:22Z" - latency: 2.478433ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:53:22Z" - latency: 2.159564ms message: 'network-check-target-ip-10-0-139-92: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:52:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T22:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-3.ec2.internal uid: c4cd74aa-03d0-438a-8356-6f3079c67ce8 resourceVersion: "61518" uid: c902bbe7-dd75-4f32-b238-bf91d1c81f77 spec: sourcePod: network-check-source-869dcfcdcd-22wpm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T22:25:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158559ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:01:22Z" - latency: 2.001465ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T23:01:22Z" - latency: 891.031µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T23:00:22Z" - latency: 1.951946ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T23:00:22Z" - latency: 931.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:59:22Z" - latency: 1.998869ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:59:22Z" - latency: 1.028706ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:58:22Z" - latency: 1.6489ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:58:22Z" - latency: 840.392µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T22:57:22Z" - latency: 2.044842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T22:57:22Z" kind: List metadata: resourceVersion: ""