apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32521" uid: 75077bd3-feb9-436c-ae0e-d816dc081985 spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-05T17:25:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 1.251975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 827.694µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 884.376µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 937.742µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 914.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:55:25Z" - latency: 983.698µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:54:25Z" - latency: 894.324µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:53:25Z" - latency: 1.732647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:52:25Z" - latency: 1.153432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:51:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32522" uid: ac36660b-0eec-4d10-8185-6aa52ccc5931 spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:24:25Z" message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.311839ms message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 7.171329ms message: 'load-balancer-api-external: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:00:25Z" - latency: 4.539972ms message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 7.432453ms message: 'load-balancer-api-external: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:59:25Z" - latency: 4.575795ms message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 7.18243ms message: 'load-balancer-api-external: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:58:25Z" - latency: 4.82453ms message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 6.153714ms message: 'load-balancer-api-external: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:57:25Z" - latency: 3.882708ms message: 'load-balancer-api-external: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 7.116895ms message: 'load-balancer-api-external: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:56:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32523" uid: 7b6f039d-1ab9-416f-8bbb-1a289214ca76 spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-05T17:24:25Z" message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.241102ms message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 7.223456ms message: 'load-balancer-api-internal: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T18:00:25Z" - latency: 4.949182ms message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 7.511808ms message: 'load-balancer-api-internal: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:59:25Z" - latency: 3.758825ms message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 7.235787ms message: 'load-balancer-api-internal: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:58:25Z" - latency: 3.888717ms message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 6.230237ms message: 'load-balancer-api-internal: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:57:25Z" - latency: 5.320079ms message: 'load-balancer-api-internal: tcp connection to acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 7.173718ms message: 'load-balancer-api-internal: resolved host name acc4052213f374db59109ffe2a74e999-fcbe810d5b688c6f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-05T17:56:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-network-check-target-ip-10-0-135-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32518" uid: 6170acd0-61fb-402f-9e2c-f00cefb9edfb spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:25Z" message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.4288ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 1.638824ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 1.899791ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 2.088567ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 1.984564ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 1.938267ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:55:25Z" - latency: 1.638017ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:54:25Z" - latency: 1.889264ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:53:25Z" - latency: 1.794797ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:52:25Z" - latency: 1.862525ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:51:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-network-check-target-ip-10-0-135-2 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32520" uid: 3c445af8-acd7-4f14-a638-d730786750aa spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:25Z" message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.360003ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 2.01325ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 2.27217ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 2.37664ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 2.248919ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 2.096102ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:55:25Z" - latency: 2.254466ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:54:25Z" - latency: 2.209974ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:53:25Z" - latency: 2.423016ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:52:25Z" - latency: 2.211975ms message: 'network-check-target-ip-10-0-135-2: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:51:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-network-check-target-ip-10-0-137-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32517" uid: 5a7cd30e-bc0e-41a0-8614-3355b67687b3 spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-05T17:25:25Z" message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.272626ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 869.507µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 1.383832ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 966.767µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 973.072µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 976.066µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:55:25Z" - latency: 892.438µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:54:25Z" - latency: 808.888µs message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:53:25Z" - latency: 1.413831ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:52:25Z" - latency: 1.285746ms message: 'network-check-target-ip-10-0-137-104: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:51:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-05T17:18:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-104.ec2.internal uid: 63666319-3010-40d0-af86-48d13f5a82b2 resourceVersion: "32519" uid: d7bbc742-3397-4e33-83de-6ac35de09d7e spec: sourcePod: network-check-source-65bdbbff45-sj8rd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-05T17:24:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.85µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T18:00:25Z" - latency: 1.617876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T18:00:25Z" - latency: 1.145539ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:59:25Z" - latency: 1.731581ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:59:25Z" - latency: 1.012957ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:58:25Z" - latency: 1.604808ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:58:25Z" - latency: 890.826µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:57:25Z" - latency: 1.819306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:57:25Z" - latency: 1.087017ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-05T17:56:25Z" - latency: 1.76073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-05T17:56:25Z" kind: List metadata: resourceVersion: ""