apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69984" uid: 0981e7b9-05d0-4914-96ff-3ca4cdcfe17f spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-26T18:22:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.090277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:04:13Z" - latency: 1.567943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 1.046565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 1.203469ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 1.439459ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 1.089825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 1.709251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:58:13Z" - latency: 914.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:57:13Z" - latency: 1.145043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:56:13Z" - latency: 1.049429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69187" uid: 3817425c-3ace-49e1-b570-71d12005336c spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T18:21:13Z" message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.591091ms message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 14.191439ms message: 'load-balancer-api-external: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:03:13Z" - latency: 4.457464ms message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 7.946257ms message: 'load-balancer-api-external: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:02:13Z" - latency: 4.370742ms message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 6.867376ms message: 'load-balancer-api-external: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:01:13Z" - latency: 4.253065ms message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 6.987756ms message: 'load-balancer-api-external: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:00:13Z" - latency: 6.257096ms message: 'load-balancer-api-external: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 9.982711ms message: 'load-balancer-api-external: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69186" uid: b3c4c6c5-7efa-4adb-83eb-2e9f4a0a7ed7 spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-26T18:21:13Z" message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.595108ms message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 14.056617ms message: 'load-balancer-api-internal: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:03:13Z" - latency: 4.455484ms message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 7.870837ms message: 'load-balancer-api-internal: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:02:13Z" - latency: 4.4136ms message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 6.763139ms message: 'load-balancer-api-internal: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:01:13Z" - latency: 4.29744ms message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 6.899631ms message: 'load-balancer-api-internal: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T19:00:13Z" - latency: 6.303629ms message: 'load-balancer-api-internal: tcp connection to a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 10.078772ms message: 'load-balancer-api-internal: resolved host name a14c296792b1f4dbe94e48be00a2de21-af40f1a167dc0a24.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-26T18:59:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-134-7 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69982" uid: 13688d6e-6067-4477-9f64-3c0e2d379d1d spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:22:13Z" message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.634413ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:04:13Z" - latency: 2.514484ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 2.211239ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 2.671827ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 2.413789ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 2.269756ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 2.878201ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:58:13Z" - latency: 2.403507ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:57:13Z" - latency: 2.43286ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:56:13Z" - latency: 2.010505ms message: 'network-check-target-ip-10-0-134-7: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-135-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69981" uid: 36dd34d4-a2c7-4861-a754-b48ca8f48681 spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:22:13Z" message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.392904ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:04:13Z" - latency: 997.168µs message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 1.737761ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 951.937µs message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 1.169574ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 1.051736ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 1.063453ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:58:13Z" - latency: 1.368494ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:57:13Z" - latency: 893.669µs message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:56:13Z" - latency: 1.020652ms message: 'network-check-target-ip-10-0-135-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-ip-10-0-138-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69983" uid: cb10f38e-7ba5-4e5d-8d04-598af7dc520d spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-26T18:22:13Z" message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.596704ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:04:13Z" - latency: 2.232259ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 2.189711ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 2.494573ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 2.497972ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 2.373277ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 2.393979ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:58:13Z" - latency: 2.333796ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:57:13Z" - latency: 2.249007ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:56:13Z" - latency: 2.402318ms message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:55:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-26T18:15:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-54-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-54.ec2.internal uid: f8da4bf8-c352-43bc-8c53-f76fc6276797 resourceVersion: "69185" uid: c76b0536-9bb2-4055-85b0-c3a026bfb49d spec: sourcePod: network-check-source-7d88cb55d8-8nwtx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-26T18:21:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152428ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:03:13Z" - latency: 2.494102ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T19:03:13Z" - latency: 843.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:02:13Z" - latency: 2.234765ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T19:02:13Z" - latency: 1.623065ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:01:13Z" - latency: 1.822004ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T19:01:13Z" - latency: 1.227725ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T19:00:13Z" - latency: 2.005453ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T19:00:13Z" - latency: 1.04092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-26T18:59:13Z" - latency: 1.924858ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-26T18:59:13Z" kind: List metadata: resourceVersion: ""