apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "39814" uid: 5e3381d5-521d-455a-a15d-5fa4114462cb spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:22:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.544225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:11:07Z" - latency: 975.484µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:10:07Z" - latency: 1.104244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 1.01709ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 1.024309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 917.06µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 1.133583ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 1.017533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:07Z" - latency: 1.232178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:07Z" - latency: 856.032µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "38792" uid: ac2c50ed-4554-4dea-a250-526afda4336e spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:21:07Z" message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.044694ms message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 7.730875ms message: 'load-balancer-api-external: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:09:07Z" - latency: 4.42552ms message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 19.365547ms message: 'load-balancer-api-external: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:08:07Z" - latency: 4.701572ms message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 8.483208ms message: 'load-balancer-api-external: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:07:07Z" - latency: 5.070379ms message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 8.990044ms message: 'load-balancer-api-external: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:06:07Z" - latency: 4.61418ms message: 'load-balancer-api-external: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 19.526272ms message: 'load-balancer-api-external: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "38791" uid: 0f84e351-383b-4149-a68d-6c3315fa0ade spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:21:07Z" message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.756206ms message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 7.829676ms message: 'load-balancer-api-internal: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:09:07Z" - latency: 4.394169ms message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 19.408722ms message: 'load-balancer-api-internal: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:08:07Z" - latency: 4.743786ms message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 8.462542ms message: 'load-balancer-api-internal: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:07:07Z" - latency: 5.068635ms message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 9.071151ms message: 'load-balancer-api-internal: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:06:07Z" - latency: 4.718075ms message: 'load-balancer-api-internal: tcp connection to ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 19.575159ms message: 'load-balancer-api-internal: resolved host name ac9bac7cc11d640ddad77e39b2db6156-4761e7cccdadec31.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-139-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "39812" uid: f0c2de86-a0c9-406a-a1ac-59b069d09af5 spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:22:07Z" message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.944387ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:11:07Z" - latency: 1.696588ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:10:07Z" - latency: 1.604992ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 15.865ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 1.615559ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 1.95444ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 15.814524ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 1.833102ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:07Z" - latency: 1.815299ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:07Z" - latency: 1.741739ms message: 'network-check-target-ip-10-0-139-96: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-141-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "39813" uid: 3c347b0a-2fc7-4304-9dd0-01bc30ab89b7 spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:22:07Z" message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.307539ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:11:07Z" - latency: 2.222962ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:10:07Z" - latency: 1.831913ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 2.05787ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 2.119845ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 1.94188ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 2.249611ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 2.094602ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:07Z" - latency: 2.149183ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:07Z" - latency: 2.208476ms message: 'network-check-target-ip-10-0-141-192: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-network-check-target-ip-10-0-143-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "39811" uid: bbe80e31-f8d1-402e-ba27-b9a7a3152d21 spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:22:07Z" message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.308µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:11:07Z" - latency: 1.20871ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:10:07Z" - latency: 817.288µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 805.298µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 1.572467ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 766.543µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 797.784µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 1.334108ms message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:07Z" - latency: 767.376µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:07Z" - latency: 867.706µs message: 'network-check-target-ip-10-0-143-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-48-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-48.ec2.internal uid: 89b14490-43ff-4d2e-9431-621354c21eec resourceVersion: "38790" uid: 8381fd8b-8bc0-4e15-8f64-3d997b2b00bc spec: sourcePod: network-check-source-7b678d77c7-hkxvh targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:21:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 759.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:09:07Z" - latency: 1.746657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:09:07Z" - latency: 828.106µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:08:07Z" - latency: 1.632007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:08:07Z" - latency: 880.803µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:07:07Z" - latency: 1.812172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:07:07Z" - latency: 833.537µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:06:07Z" - latency: 1.660566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:06:07Z" - latency: 649.435µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:05:07Z" - latency: 1.658658ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:05:07Z" kind: List metadata: resourceVersion: ""