apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "202483" uid: bc21ce2b-87bc-48a0-b850-696ce01fe7e9 spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T12:35:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.956754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:10Z" - latency: 1.033645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 1.186901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 1.538791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 1.535265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 1.076889ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 1.287419ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:10Z" - latency: 1.170656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:10Z" - latency: 1.261721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:10Z" - latency: 1.032472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "201718" uid: ed2f1a10-f719-40a2-85a5-4593c65b1792 spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:34:10Z" message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.057562ms message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 7.094867ms message: 'load-balancer-api-external: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:10Z" - latency: 17.28816ms message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 8.76732ms message: 'load-balancer-api-external: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:10Z" - latency: 13.901514ms message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 7.097593ms message: 'load-balancer-api-external: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:10Z" - latency: 16.390461ms message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 6.887463ms message: 'load-balancer-api-external: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:10Z" - latency: 18.085623ms message: 'load-balancer-api-external: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 6.98544ms message: 'load-balancer-api-external: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:54:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "201716" uid: 1e3a33d7-29f7-4792-8e05-6ee49f239c48 spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:34:10Z" message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.975963ms message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 7.119458ms message: 'load-balancer-api-internal: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:10Z" - latency: 14.210079ms message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 8.816053ms message: 'load-balancer-api-internal: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:10Z" - latency: 13.8158ms message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 7.125122ms message: 'load-balancer-api-internal: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:10Z" - latency: 16.416859ms message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 6.939542ms message: 'load-balancer-api-internal: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:10Z" - latency: 20.155388ms message: 'load-balancer-api-internal: tcp connection to ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 7.031431ms message: 'load-balancer-api-internal: resolved host name ac05bb0f26765430597987605a88e76a-abc6b6a124ab8a83.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:54:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-network-check-target-ip-10-0-128-132 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "202480" uid: 17014f67-820c-4c47-b9fe-9e82473eece7 spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:35:10Z" message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.548909ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:10Z" - latency: 2.74634ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 2.433616ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 2.520671ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 2.765783ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 2.595249ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 2.620682ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:10Z" - latency: 2.219606ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:10Z" - latency: 2.510062ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:10Z" - latency: 2.544676ms message: 'network-check-target-ip-10-0-128-132: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-network-check-target-ip-10-0-134-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "202481" uid: 68b64c9d-fec6-442a-8008-a4e4cc089b9c spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:35:10Z" message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.694783ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:10Z" - latency: 2.764227ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 2.459022ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 2.405727ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 2.611901ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 2.544523ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 2.705487ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:10Z" - latency: 2.079161ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:10Z" - latency: 2.789965ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:10Z" - latency: 2.52588ms message: 'network-check-target-ip-10-0-134-229: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-network-check-target-ip-10-0-135-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "202479" uid: 3ecd277b-2038-443e-8aaa-a26a8e9d1958 spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:35:10Z" message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140524ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:10Z" - latency: 1.042179ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 1.160372ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 1.083221ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 1.568562ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 1.124742ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 839.79µs message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:10Z" - latency: 1.16976ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:10Z" - latency: 1.094201ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:10Z" - latency: 1.548393ms message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T12:28:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-160-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-160.ec2.internal uid: d9b09e4d-7e53-426b-bcf7-387e8375c0fc resourceVersion: "201709" uid: 65991c42-c490-403c-9609-ce3c98e8a3ff spec: sourcePod: network-check-source-6f78d59f99-w9hwg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T12:34:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 884.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:10Z" - latency: 1.974978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:10Z" - latency: 1.023667ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:10Z" - latency: 1.949835ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:10Z" - latency: 878.9µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:10Z" - latency: 1.853569ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:10Z" - latency: 968.064µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:10Z" - latency: 2.179323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:10Z" - latency: 914.463µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:10Z" - latency: 1.835812ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:54:10Z" kind: List metadata: resourceVersion: ""