apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64199" uid: 38af1040-f26e-48c0-a44c-8e8db945da15 spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T11:23:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.158772ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 868.579µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 839.598µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 1.182092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 869.028µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 925.644µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:53:37Z" - latency: 1.160276ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:52:37Z" - latency: 1.204445ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:51:37Z" - latency: 1.148905ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:50:37Z" - latency: 1.68299ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64200" uid: 87c9ff94-1ac0-457a-8917-c46acf64fb9f spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T11:22:37Z" message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.104701ms message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 7.448842ms message: 'load-balancer-api-external: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:58:37Z" - latency: 4.583546ms message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 8.777426ms message: 'load-balancer-api-external: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:57:37Z" - latency: 4.655017ms message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 6.716126ms message: 'load-balancer-api-external: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:56:37Z" - latency: 3.87185ms message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 8.850759ms message: 'load-balancer-api-external: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:55:37Z" - latency: 4.492572ms message: 'load-balancer-api-external: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 8.674329ms message: 'load-balancer-api-external: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:54:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64201" uid: eb99638d-d9b8-4c54-ab67-f2d9905971e4 spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T11:22:37Z" message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.091634ms message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 7.605814ms message: 'load-balancer-api-internal: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:58:37Z" - latency: 6.020629ms message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 8.720141ms message: 'load-balancer-api-internal: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:57:37Z" - latency: 3.771932ms message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 6.804926ms message: 'load-balancer-api-internal: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:56:37Z" - latency: 4.156079ms message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 8.891003ms message: 'load-balancer-api-internal: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:55:37Z" - latency: 4.478213ms message: 'load-balancer-api-internal: tcp connection to afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 8.70942ms message: 'load-balancer-api-internal: resolved host name afbdb63c00d004da28233550d88ad3be-00f24b199ca883d3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T11:54:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-129-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64194" uid: 73fcb554-c46b-4c3e-b8f0-4837f03bcbb5 spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T11:23:37Z" message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.014719ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 1.88455ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 1.817625ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 2.016211ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 2.15222ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 1.757041ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:53:37Z" - latency: 1.949934ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:52:37Z" - latency: 2.005752ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:51:37Z" - latency: 2.051331ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:50:37Z" - latency: 2.4134ms message: 'network-check-target-ip-10-0-129-186: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-132-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64195" uid: 621a8a77-6437-4bc3-b9e1-1f76612c4af9 spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T11:23:37Z" message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.415249ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 2.330353ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 2.266684ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 2.415932ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 2.305067ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 2.295335ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:53:37Z" - latency: 2.383585ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:52:37Z" - latency: 2.321104ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:51:37Z" - latency: 2.26746ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:50:37Z" - latency: 2.419822ms message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-network-check-target-ip-10-0-132-77 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64193" uid: 5110ac62-f256-41ea-bd22-c29a27b0a18d spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T11:23:37Z" message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.926µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 1.047952ms message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 1.410095ms message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 937.288µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 987.151µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 876.282µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:53:37Z" - latency: 910.043µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:52:37Z" - latency: 931.155µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:51:37Z" - latency: 872.727µs message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:50:37Z" - latency: 1.845466ms message: 'network-check-target-ip-10-0-132-77: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:49:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T11:16:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-77-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-77.ec2.internal uid: 7372a3ff-cf90-4aae-9a61-057b2965f5fa resourceVersion: "64197" uid: 931acbb8-3509-4e12-89bb-58187bd91a3f spec: sourcePod: network-check-source-7bc5b6bf85-zsj86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T11:22:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.195973ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:58:37Z" - latency: 1.930441ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T11:58:37Z" - latency: 923.384µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:57:37Z" - latency: 1.807671ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T11:57:37Z" - latency: 993.051µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:56:37Z" - latency: 1.795298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T11:56:37Z" - latency: 1.296125ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:55:37Z" - latency: 2.087648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T11:55:37Z" - latency: 922.647µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T11:54:37Z" - latency: 1.770779ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T11:54:37Z" kind: List metadata: resourceVersion: ""