apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63077" uid: 854248b4-dce8-4503-be6d-bcf06c259295 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-20T16:24:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.746µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 972.246µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 826.051µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 1.066465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 1.179678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 1.165235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:54:20Z" - latency: 1.306646ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:53:20Z" - latency: 1.064213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:52:20Z" - latency: 1.424522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:51:20Z" - latency: 1.118713ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:50:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63078" uid: 18b3975d-0a54-466a-b8b1-d87533941723 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:23:20Z" message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.660688ms message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 7.735492ms message: 'load-balancer-api-external: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:59:20Z" - latency: 5.237858ms message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 9.779041ms message: 'load-balancer-api-external: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:58:20Z" - latency: 4.178031ms message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 10.572722ms message: 'load-balancer-api-external: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:57:20Z" - latency: 5.238423ms message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 8.637607ms message: 'load-balancer-api-external: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:56:20Z" - latency: 3.341763ms message: 'load-balancer-api-external: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 7.854584ms message: 'load-balancer-api-external: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63079" uid: 83618a7d-5997-4a0b-8693-8abcf198e4e2 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-20T16:23:20Z" message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.692585ms message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 7.776819ms message: 'load-balancer-api-internal: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:59:20Z" - latency: 6.132774ms message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 9.835174ms message: 'load-balancer-api-internal: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:58:20Z" - latency: 3.623103ms message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 10.647501ms message: 'load-balancer-api-internal: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:57:20Z" - latency: 4.234623ms message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 8.584349ms message: 'load-balancer-api-internal: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:56:20Z" - latency: 3.311799ms message: 'load-balancer-api-internal: tcp connection to a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 8.038963ms message: 'load-balancer-api-internal: resolved host name a3e745134020648b2b89a7d511702fd3-32a506b12926a49f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-20T16:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-network-check-target-ip-10-0-131-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63074" uid: d21fca07-9a9a-4f33-a036-4e53f1c1f276 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:24:20Z" message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.079432ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 2.121962ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 2.032544ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 1.852943ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 1.774332ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 2.024718ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:54:20Z" - latency: 1.900117ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:53:20Z" - latency: 2.369219ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:52:20Z" - latency: 1.990922ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:51:20Z" - latency: 1.777189ms message: 'network-check-target-ip-10-0-131-211: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:50:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-network-check-target-ip-10-0-135-221 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63075" uid: 3c33fd5c-b242-419e-b36e-597183d9711c spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:24:20Z" message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.224271ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 2.186393ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 2.011611ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 1.904075ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 2.177883ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 2.509287ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:54:20Z" - latency: 2.192747ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:53:20Z" - latency: 2.332487ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:52:20Z" - latency: 2.188178ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:51:20Z" - latency: 2.071898ms message: 'network-check-target-ip-10-0-135-221: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:50:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-network-check-target-ip-10-0-137-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63073" uid: 8e0b21b8-a0c2-4ee2-8c19-1d6950a961a8 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-20T16:24:20Z" message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004954ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 977.523µs message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 1.441628ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 1.152519ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 846.56µs message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 1.086842ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:54:20Z" - latency: 1.360582ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:53:20Z" - latency: 1.327862ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:52:20Z" - latency: 1.098883ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:51:20Z" - latency: 1.342739ms message: 'network-check-target-ip-10-0-137-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:50:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-20T16:17:19Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-195.ec2.internal uid: 55a16887-5c66-42c5-8912-da6fed5e850c resourceVersion: "63076" uid: 54d94fb7-818d-43e4-92b6-16901a23d273 spec: sourcePod: network-check-source-7bc5b6bf85-k84gj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-20T16:23:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.401µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:59:20Z" - latency: 2.056099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:59:20Z" - latency: 1.120828ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:58:20Z" - latency: 1.67643ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:58:20Z" - latency: 898.488µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:57:20Z" - latency: 2.337065ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:57:20Z" - latency: 816.571µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:56:20Z" - latency: 1.822745ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:56:20Z" - latency: 848.791µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-20T16:55:20Z" - latency: 1.916143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-20T16:55:20Z" kind: List metadata: resourceVersion: ""