apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "54287" uid: dc19b776-0aaa-4fed-baf2-473fba0ecd4f spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T00:00:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 977.516µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 824.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 928.868µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 851.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 877.855µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:19Z" - latency: 1.082091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:19Z" - latency: 1.092385ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:19Z" - latency: 817.96µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:19Z" - latency: 940.773µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:19Z" - latency: 869.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "55329" uid: cb40493c-2eec-4f75-85d4-c2bfedff6fe8 spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:59:19Z" message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.867243ms message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:19Z" - latency: 6.708467ms message: 'load-balancer-api-external: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:29:19Z" - latency: 4.399407ms message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 6.630144ms message: 'load-balancer-api-external: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:19Z" - latency: 5.343818ms message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 6.658754ms message: 'load-balancer-api-external: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:19Z" - latency: 3.85103ms message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 6.54397ms message: 'load-balancer-api-external: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:19Z" - latency: 3.7241ms message: 'load-balancer-api-external: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 6.909288ms message: 'load-balancer-api-external: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "55328" uid: 98e023a8-f2a7-433f-8cbc-f0e8d5fc1d2c spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T23:59:19Z" message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.900677ms message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:19Z" - latency: 6.6738ms message: 'load-balancer-api-internal: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:29:19Z" - latency: 4.386311ms message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 6.589895ms message: 'load-balancer-api-internal: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:19Z" - latency: 5.218916ms message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 6.68768ms message: 'load-balancer-api-internal: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:19Z" - latency: 3.951986ms message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 6.478614ms message: 'load-balancer-api-internal: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:19Z" - latency: 4.306377ms message: 'load-balancer-api-internal: tcp connection to a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 6.81784ms message: 'load-balancer-api-internal: resolved host name a5753bda9ed1e4ff483cab93ea167906-d993f7f92966af6b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-129-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "54286" uid: 152db4fb-86fe-445e-9b10-11f9eedc35d3 spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:00:19Z" message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.154009ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 2.326764ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 2.390253ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 2.251575ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 2.230425ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:19Z" - latency: 2.447923ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:19Z" - latency: 2.214829ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:19Z" - latency: 2.086934ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:19Z" - latency: 2.289088ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:19Z" - latency: 2.04723ms message: 'network-check-target-ip-10-0-129-95: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-132-169 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "54284" uid: 437998d0-c62e-4d3c-9ea3-7318eb0c2f84 spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:00:19Z" message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.858µs message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 1.006647ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 837.456µs message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 1.020832ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 1.176092ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:19Z" - latency: 1.09324ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:19Z" - latency: 1.021268ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:19Z" - latency: 1.177871ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:19Z" - latency: 1.30547ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:19Z" - latency: 1.236427ms message: 'network-check-target-ip-10-0-132-169: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-network-check-target-ip-10-0-136-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "54285" uid: c7e0c7b5-9f5b-4689-80bd-350b5143393e spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T00:00:19Z" message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.323174ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 2.510974ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 2.154279ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 2.097271ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 2.367924ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:24:19Z" - latency: 2.353811ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:23:19Z" - latency: 2.090619ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:22:19Z" - latency: 2.13436ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:21:19Z" - latency: 2.557519ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:20:19Z" - latency: 2.401881ms message: 'network-check-target-ip-10-0-136-25: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:19:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T23:53:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-169-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-169.ec2.internal uid: 47f23afb-65db-4ca4-bf58-5f744df82328 resourceVersion: "55327" uid: 0de62f3b-a2ae-4040-b091-e7b4e9aa2e04 spec: sourcePod: network-check-source-989f8b8dc-8kfsn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T23:59:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 896.536µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:29:19Z" - latency: 2.148515ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:29:19Z" - latency: 1.014653ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:28:19Z" - latency: 1.608082ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:28:19Z" - latency: 819.112µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:27:19Z" - latency: 1.805736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:27:19Z" - latency: 991.839µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:26:19Z" - latency: 1.715207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:26:19Z" - latency: 871.038µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T00:25:19Z" - latency: 1.643888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T00:25:19Z" kind: List metadata: resourceVersion: ""