apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "19748" uid: bf458e98-185c-4b52-974e-1d4c1f247ec2 spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T07:28:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.163596ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 828.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 908.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:40:43Z" - latency: 1.696944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:39:43Z" - latency: 1.084338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:38:43Z" - latency: 868.19µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:37:43Z" - latency: 1.054787ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:36:43Z" - latency: 765.838µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:35:43Z" - latency: 947.557µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:34:43Z" - latency: 775.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "20906" uid: cb4bfe27-b6aa-4b79-a5da-f3d3a502e02b spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T07:27:43Z" message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.871827ms message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:45:43Z" - latency: 7.455863ms message: 'load-balancer-api-external: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:45:43Z" - latency: 3.609372ms message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:44:43Z" - latency: 8.492006ms message: 'load-balancer-api-external: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:44:43Z" - latency: 3.93489ms message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:43:43Z" - latency: 7.763402ms message: 'load-balancer-api-external: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:43:43Z" - latency: 5.880165ms message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 8.38373ms message: 'load-balancer-api-external: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:42:43Z" - latency: 5.291077ms message: 'load-balancer-api-external: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 7.651656ms message: 'load-balancer-api-external: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:41:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "20907" uid: 2e804c1b-9198-4104-aefa-639d6acef481 spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T07:27:43Z" message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.58675ms message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:45:43Z" - latency: 7.474006ms message: 'load-balancer-api-internal: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:45:43Z" - latency: 3.834075ms message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:44:43Z" - latency: 8.526021ms message: 'load-balancer-api-internal: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:44:43Z" - latency: 4.461363ms message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:43:43Z" - latency: 7.707368ms message: 'load-balancer-api-internal: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:43:43Z" - latency: 3.840241ms message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 8.326096ms message: 'load-balancer-api-internal: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:42:43Z" - latency: 4.707214ms message: 'load-balancer-api-internal: tcp connection to ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 7.591918ms message: 'load-balancer-api-internal: resolved host name ae4b6ae4fff53445ca4ef9e3019a3847-9d604dc017569dbc.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T07:41:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-129-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "19745" uid: 31c893d1-e0ad-47b3-afa7-12380e693dd2 spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T07:28:43Z" message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 774.773µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 797.44µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 869.635µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:40:43Z" - latency: 1.483511ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:39:43Z" - latency: 1.20352ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:38:43Z" - latency: 814.206µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:37:43Z" - latency: 859.703µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:36:43Z" - latency: 837.032µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:35:43Z" - latency: 1.083594ms message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:34:43Z" - latency: 824.054µs message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-130-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "19747" uid: bf875217-2510-4997-8472-b9ff4c976fea spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T07:28:43Z" message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.103675ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 2.291167ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 2.322175ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:40:43Z" - latency: 3.083682ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:39:43Z" - latency: 2.628553ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:38:43Z" - latency: 2.475484ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:37:43Z" - latency: 2.401162ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:36:43Z" - latency: 2.37103ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:35:43Z" - latency: 2.340042ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:34:43Z" - latency: 2.414817ms message: 'network-check-target-ip-10-0-130-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-ip-10-0-130-4 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "19746" uid: fa8bd47a-0f70-42ed-a7f0-ce9f96e21aa8 spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T07:28:43Z" message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105615ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 1.834923ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 1.947961ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:40:43Z" - latency: 2.929606ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:39:43Z" - latency: 2.285996ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:38:43Z" - latency: 1.803958ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:37:43Z" - latency: 2.448974ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:36:43Z" - latency: 2.142652ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:35:43Z" - latency: 2.11687ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:34:43Z" - latency: 2.050718ms message: 'network-check-target-ip-10-0-130-4: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:33:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T07:21:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-23-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-23.ec2.internal uid: 4e32fc28-f1f4-4fdc-bdf7-d1c8ef8bdb16 resourceVersion: "20905" uid: 82638acf-a665-4da7-b404-d7551b5f3436 spec: sourcePod: network-check-source-7f44b6dd87-dwz5j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T07:27:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.429µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:45:43Z" - latency: 1.57931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T07:45:43Z" - latency: 828.984µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:44:43Z" - latency: 1.529507ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T07:44:43Z" - latency: 971.211µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:43:43Z" - latency: 1.613981ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T07:43:43Z" - latency: 924.757µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:42:43Z" - latency: 2.065829ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T07:42:43Z" - latency: 767.668µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T07:41:43Z" - latency: 1.508198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T07:41:43Z" kind: List metadata: resourceVersion: ""