apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "46478" uid: 38672c01-4e8e-4f1c-b324-9d1e8c87b3ff spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T18:14:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.124832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 1.162532ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 732.906µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 1.220293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:32:30Z" - latency: 1.566593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:31:30Z" - latency: 1.110655ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:30:30Z" - latency: 1.193249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:29:30Z" - latency: 1.533093ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:28:30Z" - latency: 1.153165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:27:30Z" - latency: 1.07535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:26:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "48681" uid: 990ab55c-d9b7-4038-b01d-47a87793132f spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:13:31Z" message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.697757ms message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:37:30Z" - latency: 6.637218ms message: 'load-balancer-api-external: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:37:30Z" - latency: 5.474571ms message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:36:30Z" - latency: 7.039385ms message: 'load-balancer-api-external: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:36:30Z" - latency: 5.606758ms message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 7.140214ms message: 'load-balancer-api-external: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:35:30Z" - latency: 5.430313ms message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 7.396887ms message: 'load-balancer-api-external: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:34:30Z" - latency: 4.046862ms message: 'load-balancer-api-external: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 6.803935ms message: 'load-balancer-api-external: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:33:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "48680" uid: d7afc9e8-5bfe-4858-bd45-2b55b8204d33 spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:13:31Z" message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.820069ms message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:37:30Z" - latency: 6.671066ms message: 'load-balancer-api-internal: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:37:30Z" - latency: 5.415694ms message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:36:30Z" - latency: 6.8056ms message: 'load-balancer-api-internal: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:36:30Z" - latency: 5.543882ms message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 7.187374ms message: 'load-balancer-api-internal: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:35:30Z" - latency: 5.410741ms message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 7.432585ms message: 'load-balancer-api-internal: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:34:30Z" - latency: 4.035058ms message: 'load-balancer-api-internal: tcp connection to a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 6.928021ms message: 'load-balancer-api-internal: resolved host name a21ec72edbdf2493482feaad30803a22-96a2651c09aecc3b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T18:33:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-131-126 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "46476" uid: cb46017a-3d98-40ce-80b6-59545968be88 spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:14:30Z" message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.198456ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 1.932121ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 1.717065ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 1.845645ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:32:30Z" - latency: 1.940481ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:31:30Z" - latency: 1.846461ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:30:30Z" - latency: 1.896365ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:29:30Z" - latency: 2.320433ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:28:30Z" - latency: 1.815898ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:27:30Z" - latency: 1.832203ms message: 'network-check-target-ip-10-0-131-126: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:26:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-137-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "46475" uid: 8c261c7c-7b00-47a8-bcbf-097ffec502e9 spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:14:30Z" message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.112099ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 1.923383ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 1.941624ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 1.875408ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:32:30Z" - latency: 2.391298ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:31:30Z" - latency: 2.288547ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:30:30Z" - latency: 2.0736ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:29:30Z" - latency: 2.209925ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:28:30Z" - latency: 2.09328ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:27:30Z" - latency: 1.965493ms message: 'network-check-target-ip-10-0-137-15: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:26:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-ip-10-0-141-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "46474" uid: 51e953d0-e5eb-40e2-adda-48e078619d6a spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:14:30Z" message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.824µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 1.020699ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 1.376313ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 947.431µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:32:30Z" - latency: 1.779141ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:31:30Z" - latency: 965.88µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:30:30Z" - latency: 961.866µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:29:30Z" - latency: 1.854415ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:28:30Z" - latency: 878.056µs message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:27:30Z" - latency: 1.051865ms message: 'network-check-target-ip-10-0-141-56: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:26:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:07:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-56-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-56.ec2.internal uid: 950eb056-324c-4443-801b-9c12fa2a6754 resourceVersion: "48679" uid: f8dff36a-7852-4f8f-9768-42dd902a424b spec: sourcePod: network-check-source-989f8b8dc-57w86 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T18:13:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:37:30Z" - latency: 2.271262ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:37:30Z" - latency: 879.485µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:36:30Z" - latency: 2.114477ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:36:30Z" - latency: 936.226µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:35:30Z" - latency: 2.218275ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:35:30Z" - latency: 1.025315ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:34:30Z" - latency: 2.05624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:34:30Z" - latency: 946.876µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T18:33:30Z" - latency: 2.068936ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T18:33:30Z" kind: List metadata: resourceVersion: ""