apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "19684" uid: f7fdc477-6c89-4d8f-a364-76c5ff43a1eb spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T12:30:12Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 874.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 987.697µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:42:12Z" - latency: 1.246498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:41:12Z" - latency: 1.030739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:40:12Z" - latency: 1.994263ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:39:12Z" - latency: 879.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:38:12Z" - latency: 903.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:37:12Z" - latency: 848.865µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:36:12Z" - latency: 785.585µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:35:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "20908" uid: 8b842faf-3d42-4813-837b-e7c18c409800 spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T12:29:12Z" message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.498356ms message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:47:12Z" - latency: 7.762104ms message: 'load-balancer-api-external: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:47:12Z" - latency: 6.093009ms message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:46:12Z" - latency: 7.928554ms message: 'load-balancer-api-external: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:46:12Z" - latency: 5.625786ms message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:45:12Z" - latency: 7.284788ms message: 'load-balancer-api-external: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:45:12Z" - latency: 5.626022ms message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 6.652485ms message: 'load-balancer-api-external: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:44:12Z" - latency: 4.783465ms message: 'load-balancer-api-external: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 7.200466ms message: 'load-balancer-api-external: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:43:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "20909" uid: b17265a6-ca84-4e1e-bdaf-d56aea91a350 spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T12:29:12Z" message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.270387ms message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:47:12Z" - latency: 7.708511ms message: 'load-balancer-api-internal: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:47:12Z" - latency: 5.990254ms message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:46:12Z" - latency: 9.104286ms message: 'load-balancer-api-internal: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:46:12Z" - latency: 5.594094ms message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:45:12Z" - latency: 7.334536ms message: 'load-balancer-api-internal: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:45:12Z" - latency: 5.618525ms message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 6.694583ms message: 'load-balancer-api-internal: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:44:12Z" - latency: 4.959186ms message: 'load-balancer-api-internal: tcp connection to aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 7.16262ms message: 'load-balancer-api-internal: resolved host name aae612656d7d540c58f8a94618823812-12edab36b9c73df6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T12:43:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-network-check-target-ip-10-0-129-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "19683" uid: 94f1c6bb-174d-4929-9ff7-8313c1acd569 spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T12:30:12Z" message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.007681ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 1.667619ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 1.88511ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:42:12Z" - latency: 2.029495ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:41:12Z" - latency: 2.006106ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:40:12Z" - latency: 2.648668ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:39:12Z" - latency: 1.777917ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:38:12Z" - latency: 2.010855ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:37:12Z" - latency: 1.933315ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:36:12Z" - latency: 1.747055ms message: 'network-check-target-ip-10-0-129-192: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:35:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-network-check-target-ip-10-0-135-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "19682" uid: 376f8860-0c17-4be8-b016-f90128f3521f spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T12:30:12Z" message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.337998ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 1.861105ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 1.909956ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:42:12Z" - latency: 2.025999ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:41:12Z" - latency: 2.062725ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:40:12Z" - latency: 2.913153ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:39:12Z" - latency: 1.835792ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:38:12Z" - latency: 2.329003ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:37:12Z" - latency: 1.869213ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:36:12Z" - latency: 1.845047ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:35:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-network-check-target-ip-10-0-143-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "19681" uid: a7875833-4bf5-42db-826b-8b9c36bddf68 spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-08-05T12:30:12Z" message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 787.687µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 899.878µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 1.010563ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:42:12Z" - latency: 804.837µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:41:12Z" - latency: 704.363µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:40:12Z" - latency: 2.399423ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:39:12Z" - latency: 834.375µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:38:12Z" - latency: 1.395648ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:37:12Z" - latency: 857.379µs message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:36:12Z" - latency: 1.131238ms message: 'network-check-target-ip-10-0-143-178: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:35:12Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T12:23:11Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-178-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-178.ec2.internal uid: fe02761d-1f46-4628-8afd-5d2ffa115e71 resourceVersion: "20907" uid: acc7198b-b9b1-4f5f-8468-240ba1a28f85 spec: sourcePod: network-check-source-65bdbbff45-dq9dj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T12:29:12Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.142µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:47:12Z" - latency: 2.538303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T12:47:12Z" - latency: 1.022644ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:46:12Z" - latency: 2.210083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T12:46:12Z" - latency: 2.068358ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:45:12Z" - latency: 1.714543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T12:45:12Z" - latency: 841.881µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:44:12Z" - latency: 1.726024ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T12:44:12Z" - latency: 928.408µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T12:43:12Z" - latency: 1.767216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T12:43:12Z" kind: List metadata: resourceVersion: ""