apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "55659" uid: d16565e5-f575-4022-baed-f8aa8a27b6e2 spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T14:16:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 754.679µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 741.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 671.472µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 676.631µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:34:30Z" - latency: 792.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:33:30Z" - latency: 668.009µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:32:30Z" - latency: 886.257µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:31:30Z" - latency: 863.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:30:30Z" - latency: 663.611µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:29:30Z" - latency: 718.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:28:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "58140" uid: 47d98859-2fb4-44d8-8c37-851f441d6d60 spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T14:15:30Z" message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.439068ms message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:30Z" - latency: 2.354596ms message: 'load-balancer-api-external: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:39:30Z" - latency: 17.240551ms message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:30Z" - latency: 3.606302ms message: 'load-balancer-api-external: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:38:30Z" - latency: 14.536578ms message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 2.847723ms message: 'load-balancer-api-external: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:37:30Z" - latency: 14.979641ms message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 2.279213ms message: 'load-balancer-api-external: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:36:30Z" - latency: 15.595058ms message: 'load-balancer-api-external: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 4.21531ms message: 'load-balancer-api-external: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:35:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "58138" uid: d9090bd9-d28c-49d7-810b-759a70ef88ac spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T14:15:30Z" message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.74273ms message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:30Z" - latency: 7.495224ms message: 'load-balancer-api-internal: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:39:30Z" - latency: 16.21514ms message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:30Z" - latency: 7.145246ms message: 'load-balancer-api-internal: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:38:30Z" - latency: 18.242322ms message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 7.825754ms message: 'load-balancer-api-internal: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:37:30Z" - latency: 25.818988ms message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 6.473391ms message: 'load-balancer-api-internal: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:36:30Z" - latency: 17.053499ms message: 'load-balancer-api-internal: tcp connection to a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 8.121666ms message: 'load-balancer-api-internal: resolved host name a915e5835840d4879bd1c2c8f103fa69-33cc1b15d3d35aa2.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:35:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-129-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "55654" uid: daf22188-b686-41ef-a7d4-8bf20e0e5098 spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:16:30Z" message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 769.446µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 468.967µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 445.331µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 738.809µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:34:30Z" - latency: 499.476µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:33:30Z" - latency: 728.953µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:32:30Z" - latency: 760.901µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:31:30Z" - latency: 461.231µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:30:30Z" - latency: 445.385µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:29:30Z" - latency: 707.088µs message: 'network-check-target-ip-10-0-129-158: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:28:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-130-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "55657" uid: 77f87482-ccfd-4bb8-844c-50352198670d spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:16:30Z" message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.888339ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 1.506051ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 1.710384ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 2.005073ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:34:30Z" - latency: 1.887172ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:33:30Z" - latency: 1.730946ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:32:30Z" - latency: 546.052µs message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:31:30Z" - latency: 1.857109ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:30:30Z" - latency: 1.8601ms message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:29:30Z" - latency: 589.95µs message: 'network-check-target-ip-10-0-130-107: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:28:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-ip-10-0-132-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "55655" uid: 75293861-5361-446a-940b-fa2881e7a24c spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:16:30Z" message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 600.059µs message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 1.752123ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 1.657435ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 622.008µs message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:34:30Z" - latency: 2.046515ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:33:30Z" - latency: 579.269µs message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:32:30Z" - latency: 1.445464ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:31:30Z" - latency: 1.5868ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:30:30Z" - latency: 1.585699ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:29:30Z" - latency: 1.404707ms message: 'network-check-target-ip-10-0-132-7: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:28:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:09:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-158-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-158.ec2.internal uid: 476e694c-ed97-4e99-818e-d21053d5e8f2 resourceVersion: "58137" uid: 0b711820-e576-44db-8d33-2354e1b02861 spec: sourcePod: network-check-source-6f78d59f99-2sxp4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T14:15:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.088448ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:39:30Z" - latency: 539.832µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:39:30Z" - latency: 2.260967ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:38:30Z" - latency: 660.042µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:38:30Z" - latency: 2.021104ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:37:30Z" - latency: 681.106µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:37:30Z" - latency: 1.070379ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:36:30Z" - latency: 531.637µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:36:30Z" - latency: 1.036632ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:35:30Z" - latency: 537.038µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:35:30Z" kind: List metadata: resourceVersion: ""