apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "43840" uid: a6b87d6d-a29d-4ed7-8554-c02430f5bc3c spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T18:26:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 919.646µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 1.000407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 1.392551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 1.004036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:05Z" - latency: 885.113µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:43:05Z" - latency: 998.727µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:42:05Z" - latency: 1.152385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:05Z" - latency: 1.05246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:05Z" - latency: 1.004115ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:05Z" - latency: 1.405385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "45706" uid: 0b420477-b6d7-43a3-ba05-b82947bb1a66 spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:25:05Z" message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.94992ms message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:05Z" - latency: 14.180636ms message: 'load-balancer-api-external: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:49:05Z" - latency: 3.32478ms message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:05Z" - latency: 9.041256ms message: 'load-balancer-api-external: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:48:05Z" - latency: 5.015577ms message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 11.91216ms message: 'load-balancer-api-external: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:47:05Z" - latency: 5.039258ms message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 8.884868ms message: 'load-balancer-api-external: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:46:05Z" - latency: 4.007205ms message: 'load-balancer-api-external: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 8.042311ms message: 'load-balancer-api-external: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "45707" uid: 3555bcc1-c61d-4a04-b90b-9dba5d1ad7eb spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T18:25:05Z" message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.06784ms message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:05Z" - latency: 13.469996ms message: 'load-balancer-api-internal: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:49:05Z" - latency: 3.287212ms message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:05Z" - latency: 9.125943ms message: 'load-balancer-api-internal: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:48:05Z" - latency: 4.990551ms message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 11.939657ms message: 'load-balancer-api-internal: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:47:05Z" - latency: 4.439464ms message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 8.875799ms message: 'load-balancer-api-internal: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:46:05Z" - latency: 3.607317ms message: 'load-balancer-api-internal: tcp connection to ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 7.994789ms message: 'load-balancer-api-internal: resolved host name ac26382936ae24d7a9bff706f872d57e-2bf8f92b17301faf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-network-check-target-ip-10-0-138-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "43839" uid: 78344c27-34ad-4e78-acd8-7af6328c98f8 spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:26:05Z" message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.578354ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 2.873611ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 2.165378ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 2.307782ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:05Z" - latency: 2.471562ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:43:05Z" - latency: 2.691372ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:42:05Z" - latency: 2.407962ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:05Z" - latency: 2.610929ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:05Z" - latency: 2.319893ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:05Z" - latency: 2.35533ms message: 'network-check-target-ip-10-0-138-244: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-network-check-target-ip-10-0-141-59 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "43837" uid: 528e8cf9-d7c3-4bec-a2a9-e169f8823bd9 spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:26:05Z" message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.324µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 745.815µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 817.525µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 836.883µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:05Z" - latency: 779.114µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:43:05Z" - latency: 1.411335ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:42:05Z" - latency: 1.097959ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:05Z" - latency: 1.147454ms message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:05Z" - latency: 861.587µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:05Z" - latency: 738.443µs message: 'network-check-target-ip-10-0-141-59: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-network-check-target-ip-10-0-143-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "43838" uid: 4121f4ff-e287-4975-a181-1b68e1a6da3b spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T18:26:05Z" message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.034379ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 2.021871ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 2.112126ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 1.922217ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:44:05Z" - latency: 2.399469ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:43:05Z" - latency: 1.967225ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:42:05Z" - latency: 2.057384ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:41:05Z" - latency: 2.145121ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:40:05Z" - latency: 2.014654ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:39:05Z" - latency: 2.038241ms message: 'network-check-target-ip-10-0-143-212: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:38:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T18:19:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-59-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-59.ec2.internal uid: 67891eb8-9594-4671-9e90-58b8e7775df7 resourceVersion: "45704" uid: c8bde8f0-e225-4960-8b15-46eaea73099f spec: sourcePod: network-check-source-7f44b6dd87-j7vs8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T18:25:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.079657ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:49:05Z" - latency: 3.606924ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:49:05Z" - latency: 957.931µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:48:05Z" - latency: 1.573108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:48:05Z" - latency: 667.09µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:47:05Z" - latency: 1.654488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:47:05Z" - latency: 1.428909ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:46:05Z" - latency: 1.568979ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:46:05Z" - latency: 856.793µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:45:05Z" - latency: 2.150378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:45:05Z" kind: List metadata: resourceVersion: ""