apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "39567" uid: 96a49938-6481-4337-a882-29052a8f1c5e spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T18:39:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.549647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 1.152042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 1.118079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:35Z" - latency: 851.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:35Z" - latency: 846.991µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:35Z" - latency: 1.066108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:35Z" - latency: 881.344µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:35Z" - latency: 1.086239ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:46:35Z" - latency: 1.014136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:45:35Z" - latency: 1.106673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "42066" uid: dfcb8214-4e2e-4aa8-9f23-0ae422a7bf97 spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:38:35Z" message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.036487ms message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:35Z" - latency: 8.560908ms message: 'load-balancer-api-external: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:35Z" - latency: 5.402922ms message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:35Z" - latency: 12.664902ms message: 'load-balancer-api-external: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:35Z" - latency: 8.707034ms message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:35Z" - latency: 7.678609ms message: 'load-balancer-api-external: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:35Z" - latency: 3.444554ms message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 13.424743ms message: 'load-balancer-api-external: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:35Z" - latency: 5.085654ms message: 'load-balancer-api-external: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 11.154885ms message: 'load-balancer-api-external: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "42065" uid: dd53f4c1-e0ea-4a3e-98cb-a6f34de2e6ab spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T18:38:35Z" message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.701757ms message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:35Z" - latency: 8.50272ms message: 'load-balancer-api-internal: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:35Z" - latency: 5.410546ms message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:35Z" - latency: 12.574259ms message: 'load-balancer-api-internal: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:35Z" - latency: 4.626949ms message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:35Z" - latency: 7.730725ms message: 'load-balancer-api-internal: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:35Z" - latency: 7.80203ms message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 13.407069ms message: 'load-balancer-api-internal: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:35Z" - latency: 4.336784ms message: 'load-balancer-api-internal: tcp connection to a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 11.203612ms message: 'load-balancer-api-internal: resolved host name a20a3f04b2656484a824c0ce3de6a642-edcdf609d8196732.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T18:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-134-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "39565" uid: eec15410-0177-4d9d-862b-be048706394f spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:39:35Z" message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.581496ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 2.373927ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 2.234257ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:35Z" - latency: 2.321429ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:35Z" - latency: 2.269887ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:35Z" - latency: 2.303449ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:35Z" - latency: 2.160695ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:35Z" - latency: 2.353822ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:46:35Z" - latency: 2.475942ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:45:35Z" - latency: 2.370316ms message: 'network-check-target-ip-10-0-134-241: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-136-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "39566" uid: 153fa8ed-46ff-48dd-90d5-6646d7e94893 spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:39:35Z" message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.557189ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 2.633565ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 2.174827ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:35Z" - latency: 2.080594ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:35Z" - latency: 2.036915ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:35Z" - latency: 2.308432ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:35Z" - latency: 2.225653ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:35Z" - latency: 2.20817ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:46:35Z" - latency: 1.93102ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:45:35Z" - latency: 2.30384ms message: 'network-check-target-ip-10-0-136-57: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-ip-10-0-138-224 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "39564" uid: 81ca0378-9ee8-4256-98cd-f4f6f2ababfb spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T18:39:35Z" message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 720.428µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 778.09µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 867.282µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:51:35Z" - latency: 1.348735ms message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:50:35Z" - latency: 882.437µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:49:35Z" - latency: 1.022506ms message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:48:35Z" - latency: 979.585µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:47:35Z" - latency: 927.123µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:46:35Z" - latency: 886.122µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:45:35Z" - latency: 954.007µs message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:44:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T18:32:34Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-224-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-224.ec2.internal uid: c1f7313b-ed0f-47d0-a000-f4ee6e3b14dd resourceVersion: "42064" uid: 71d863bc-d7c8-4ceb-88dc-374b14d2f2ba spec: sourcePod: network-check-source-869dcfcdcd-h5p2f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T18:38:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.451µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:56:35Z" - latency: 2.071615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:56:35Z" - latency: 697.878µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:55:35Z" - latency: 1.807232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:55:35Z" - latency: 800.376µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:54:35Z" - latency: 1.635074ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:54:35Z" - latency: 805.348µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:53:35Z" - latency: 2.6202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:53:35Z" - latency: 1.154058ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T18:52:35Z" - latency: 1.588122ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T18:52:35Z" kind: List metadata: resourceVersion: ""