apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28240" uid: a366ea43-49b5-4993-8f3f-dd08291eb4cc spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T18:46:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.807875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:28:27Z" - latency: 987.97µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 1.028954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 852.565µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 1.208737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 1.086365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 1.236731ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:22:27Z" - latency: 1.789383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:21:27Z" - latency: 1.284347ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:20:27Z" - latency: 993.094µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28005" uid: 543b8bda-59c1-40fc-a72b-59c60c17a406 spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T18:45:27Z" message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.497543ms message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 7.287104ms message: 'load-balancer-api-external: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:27:27Z" - latency: 51.600981ms message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 6.674125ms message: 'load-balancer-api-external: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:26:27Z" - latency: 51.549167ms message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 6.37103ms message: 'load-balancer-api-external: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:25:27Z" - latency: 55.528307ms message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 6.606783ms message: 'load-balancer-api-external: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:24:27Z" - latency: 51.562636ms message: 'load-balancer-api-external: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 7.440605ms message: 'load-balancer-api-external: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:23:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28004" uid: 1b597c9b-e20e-4b7d-adf1-8c70bb4566a3 spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T18:45:27Z" message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.82212ms message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 7.313928ms message: 'load-balancer-api-internal: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:27:27Z" - latency: 54.447068ms message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 6.62081ms message: 'load-balancer-api-internal: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:26:27Z" - latency: 51.543619ms message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 6.481535ms message: 'load-balancer-api-internal: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:25:27Z" - latency: 56.694026ms message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 6.558958ms message: 'load-balancer-api-internal: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:24:27Z" - latency: 52.376124ms message: 'load-balancer-api-internal: tcp connection to ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 7.479626ms message: 'load-balancer-api-internal: resolved host name ab53e71aabeb04af4b6344fe1a3d0bb8-6906b96c74f98d04.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T19:23:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-134-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28237" uid: b7adc67e-e2d8-46e2-a6b3-e15748cb36fe spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T18:46:27Z" message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.609µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:28:27Z" - latency: 1.384547ms message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 1.709951ms message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 794.838µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 982.321µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 867.541µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 843.506µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:22:27Z" - latency: 984.596µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:21:27Z" - latency: 944.782µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:20:27Z" - latency: 984.225µs message: 'network-check-target-ip-10-0-134-253: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-135-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28239" uid: f457b667-046b-4d5e-baca-5381c2937897 spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T18:46:27Z" message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.340916ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:28:27Z" - latency: 2.317754ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 2.290277ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 2.029256ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 2.44682ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 2.511671ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 2.490832ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:22:27Z" - latency: 2.805824ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:21:27Z" - latency: 2.650936ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:20:27Z" - latency: 1.861606ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-network-check-target-ip-10-0-140-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28238" uid: 6e29f06e-35d1-4c4b-b9e0-1f1942b90d96 spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T18:46:27Z" message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.42075ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:28:27Z" - latency: 2.169799ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 2.066286ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 2.615444ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 2.336348ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 2.239301ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 2.37582ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:22:27Z" - latency: 2.185166ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:21:27Z" - latency: 2.534588ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:20:27Z" - latency: 2.382552ms message: 'network-check-target-ip-10-0-140-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:19:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T18:39:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-253-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-253.us-west-2.compute.internal uid: 40407ef8-37e2-41c0-8ea7-440485142fe7 resourceVersion: "28003" uid: eb952dae-2742-4966-a104-4e18e031c343 spec: sourcePod: network-check-source-6f78d59f99-lk8nd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T18:45:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 763.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:27:27Z" - latency: 2.255932ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:27:27Z" - latency: 834.374µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:26:27Z" - latency: 1.72984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:26:27Z" - latency: 900.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:25:27Z" - latency: 1.738173ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:25:27Z" - latency: 838.739µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:24:27Z" - latency: 1.88653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:24:27Z" - latency: 1.00718ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T19:23:27Z" - latency: 2.147073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T19:23:27Z" kind: List metadata: resourceVersion: ""