apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "43079" uid: 559c0cb7-384a-4d30-b1ae-d2810e71407b spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T17:27:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 908.424µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 1.191442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 1.150729ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 1.077105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:23Z" - latency: 971.119µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:23Z" - latency: 1.303954ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:23Z" - latency: 1.043311ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:23Z" - latency: 1.28935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:23Z" - latency: 989.954µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:23Z" - latency: 1.102538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "45275" uid: b70540a5-1ae0-49e9-b688-5db8a5a24532 spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:26:23Z" message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.375328ms message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:23Z" - latency: 6.680661ms message: 'load-balancer-api-external: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:23Z" - latency: 4.270621ms message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:23Z" - latency: 6.821691ms message: 'load-balancer-api-external: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:23Z" - latency: 5.523971ms message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 6.86268ms message: 'load-balancer-api-external: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:23Z" - latency: 4.709763ms message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 8.259946ms message: 'load-balancer-api-external: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:23Z" - latency: 5.782169ms message: 'load-balancer-api-external: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 7.972429ms message: 'load-balancer-api-external: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:46:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "45276" uid: ff31cc22-722f-441f-bdd2-ca0ffee52c82 spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:26:23Z" message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.907685ms message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:23Z" - latency: 6.73481ms message: 'load-balancer-api-internal: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:23Z" - latency: 3.828449ms message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:23Z" - latency: 6.85325ms message: 'load-balancer-api-internal: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:23Z" - latency: 3.990959ms message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 6.836673ms message: 'load-balancer-api-internal: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:23Z" - latency: 3.981918ms message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 8.289793ms message: 'load-balancer-api-internal: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:23Z" - latency: 5.83442ms message: 'load-balancer-api-internal: tcp connection to a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 7.933178ms message: 'load-balancer-api-internal: resolved host name a2a1e3973e827483aaabd9614b7588db-e4cf71d60d0f9915.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:46:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-network-check-target-ip-10-0-128-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "43077" uid: 5dc3848a-292c-424e-accf-a7514ef5b16c spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:27:23Z" message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.141799ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 1.847683ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 1.961825ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 1.813723ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:23Z" - latency: 1.973054ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:23Z" - latency: 1.852351ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:23Z" - latency: 2.338696ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:23Z" - latency: 2.140922ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:23Z" - latency: 1.986048ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:23Z" - latency: 1.979934ms message: 'network-check-target-ip-10-0-128-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-network-check-target-ip-10-0-132-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "43076" uid: 313726e9-d27d-4980-add1-70274430131d spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:27:23Z" message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 740.137µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 1.264189ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 797.009µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 1.329617ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:23Z" - latency: 988.999µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:23Z" - latency: 898.575µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:23Z" - latency: 1.563223ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:23Z" - latency: 1.424973ms message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:23Z" - latency: 924.045µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:23Z" - latency: 850.175µs message: 'network-check-target-ip-10-0-132-206: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-network-check-target-ip-10-0-138-128 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "43078" uid: d6fcd901-885b-4f0c-b3a9-b24e3c541409 spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:27:23Z" message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.098494ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 2.200492ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 2.110021ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 2.010795ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:23Z" - latency: 2.16172ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:23Z" - latency: 2.17706ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:23Z" - latency: 2.182207ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:23Z" - latency: 2.355319ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:23Z" - latency: 2.122463ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:40:23Z" - latency: 1.995318ms message: 'network-check-target-ip-10-0-138-128: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:39:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:20:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-206-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-206.ec2.internal uid: da4a0a5d-8ba1-407e-acdf-1a50ccd44936 resourceVersion: "45274" uid: 402cef1c-eef4-40b7-9287-8dd5073326d6 spec: sourcePod: network-check-source-7f44b6dd87-v7h9s targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T17:26:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.687µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:23Z" - latency: 1.757809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:23Z" - latency: 890.236µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:23Z" - latency: 1.621138ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:23Z" - latency: 1.247365ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:23Z" - latency: 1.741724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:23Z" - latency: 893.002µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:23Z" - latency: 1.912237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:47:23Z" - latency: 725.203µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:23Z" - latency: 1.864315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:46:23Z" kind: List metadata: resourceVersion: ""