apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "51630" uid: 486afc43-acbf-4a00-987a-a026f29f37e1 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T16:45:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.022382ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:13:41Z" - latency: 1.342597ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:12:41Z" - latency: 921.773µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:11:41Z" - latency: 1.105647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:10:41Z" - latency: 864.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:09:41Z" - latency: 1.085435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 1.64801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 1.352141ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 1.205428ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 911.67µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "46205" uid: a7ca9e31-04ba-4e4f-a81f-183457093029 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:44:41Z" message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.7479ms message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 8.757511ms message: 'load-balancer-api-external: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:08:41Z" - latency: 6.030331ms message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 14.029213ms message: 'load-balancer-api-external: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:07:41Z" - latency: 5.39358ms message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 7.624147ms message: 'load-balancer-api-external: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:41Z" - latency: 4.186492ms message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 9.233309ms message: 'load-balancer-api-external: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:41Z" - latency: 4.625241ms message: 'load-balancer-api-external: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - latency: 8.434736ms message: 'load-balancer-api-external: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "46206" uid: e3494a9a-2ed7-486a-a3fc-496124f562ad spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:44:41Z" message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.157761ms message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 8.822479ms message: 'load-balancer-api-internal: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:08:41Z" - latency: 4.064263ms message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 13.950991ms message: 'load-balancer-api-internal: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:07:41Z" - latency: 5.326051ms message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 7.741595ms message: 'load-balancer-api-internal: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:41Z" - latency: 4.245668ms message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 9.140615ms message: 'load-balancer-api-internal: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:41Z" - latency: 4.648097ms message: 'load-balancer-api-internal: tcp connection to acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - latency: 8.466121ms message: 'load-balancer-api-internal: resolved host name acea51cd548aa4916b34dd13d308909f-f80f2a2c9d0da880.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-network-check-target-ip-10-0-129-139 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "51629" uid: 6b6498cd-c441-4095-a483-b28be26698c2 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:41Z" message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.514074ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:13:41Z" - latency: 2.412888ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:12:41Z" - latency: 2.139366ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:11:41Z" - latency: 2.387357ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:10:41Z" - latency: 2.296025ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:09:41Z" - latency: 2.861013ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 2.366749ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 2.295243ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 2.091157ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 2.344937ms message: 'network-check-target-ip-10-0-129-139: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-network-check-target-ip-10-0-136-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "51628" uid: d12212f8-4623-4c3f-8114-759d19da1863 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:41Z" message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.266431ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:13:41Z" - latency: 2.102714ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:12:41Z" - latency: 1.880143ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:11:41Z" - latency: 1.895271ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:10:41Z" - latency: 2.067978ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:09:41Z" - latency: 1.911851ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 2.124032ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 1.889365ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 2.143842ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 1.839516ms message: 'network-check-target-ip-10-0-136-232: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-network-check-target-ip-10-0-137-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "51627" uid: 11fbddac-7e72-48e6-9e5e-eb956ad5dee9 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:45:41Z" message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.293973ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:13:41Z" - latency: 984.033µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:12:41Z" - latency: 878.272µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:11:41Z" - latency: 952.924µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:10:41Z" - latency: 974.047µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:09:41Z" - latency: 922.419µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 981.674µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 975.435µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 918.222µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 880.012µs message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:38:40Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-39-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-39.ec2.internal uid: a3cf864d-7ef1-4b69-962e-07e28a3538c7 resourceVersion: "46203" uid: 7e09a715-1497-4971-9f7c-0946356cfe39 spec: sourcePod: network-check-source-dbd9cf844-bxk2l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T16:44:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.342863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:08:41Z" - latency: 1.827699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:08:41Z" - latency: 1.694725ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:07:41Z" - latency: 2.08269ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:07:41Z" - latency: 1.225878ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:41Z" - latency: 1.980367ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:41Z" - latency: 1.17706ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:41Z" - latency: 2.012916ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:41Z" - latency: 821.502µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:41Z" - latency: 1.65938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:41Z" kind: List metadata: resourceVersion: ""