apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "78307" uid: 9a0ff0d7-8828-41b1-89b2-b8c2c1e64124 spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-27T18:40:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 800.841µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:28Z" - latency: 912.747µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:28Z" - latency: 866.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:20:28Z" - latency: 945.544µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:19:28Z" - latency: 1.154944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:18:28Z" - latency: 1.078264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:17:28Z" - latency: 1.161975ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:16:28Z" - latency: 941.651µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:15:28Z" - latency: 1.329448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:14:28Z" - latency: 1.043403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "88134" uid: e3d0f18f-5115-4d2f-90e1-49e26c6005aa spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T18:39:28Z" message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.253294ms message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:28Z" - latency: 9.474497ms message: 'load-balancer-api-external: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:28Z" - latency: 4.250213ms message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:28Z" - latency: 12.684785ms message: 'load-balancer-api-external: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:28Z" - latency: 5.95926ms message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:28Z" - latency: 7.424222ms message: 'load-balancer-api-external: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:28Z" - latency: 4.847677ms message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:28Z" - latency: 9.957956ms message: 'load-balancer-api-external: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:28Z" - latency: 11.547639ms message: 'load-balancer-api-external: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:28Z" - latency: 8.923819ms message: 'load-balancer-api-external: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:23:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "88136" uid: b4f4ffb4-ae04-42fb-8c6f-d6ac60612042 spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-27T18:39:28Z" message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 47.979278ms message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:28Z" - latency: 9.33127ms message: 'load-balancer-api-internal: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:28Z" - latency: 4.283762ms message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:28Z" - latency: 12.482157ms message: 'load-balancer-api-internal: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:28Z" - latency: 5.384288ms message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:28Z" - latency: 7.311179ms message: 'load-balancer-api-internal: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:28Z" - latency: 4.85326ms message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:28Z" - latency: 9.699929ms message: 'load-balancer-api-internal: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:28Z" - latency: 5.982194ms message: 'load-balancer-api-internal: tcp connection to a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:28Z" - latency: 8.769195ms message: 'load-balancer-api-internal: resolved host name a21232e2c335645078a0372e432f61e3-d6350540945ea601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-27T19:23:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-network-check-target-ip-10-0-128-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "78308" uid: 9699c365-48c7-4b7c-9aa0-d74959ba5b35 spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:40:28Z" message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.72724ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:28Z" - latency: 2.455783ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:28Z" - latency: 1.935051ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:20:28Z" - latency: 2.387009ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:19:28Z" - latency: 1.902914ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:18:28Z" - latency: 2.633048ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:17:28Z" - latency: 2.280428ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:16:28Z" - latency: 2.284314ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:15:28Z" - latency: 2.371673ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:14:28Z" - latency: 2.429026ms message: 'network-check-target-ip-10-0-128-196: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-network-check-target-ip-10-0-128-32 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "78305" uid: b49ce5a3-51db-489b-8c9a-e3da5ac2872a spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:40:28Z" message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 704.725µs message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:28Z" - latency: 882.841µs message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:28Z" - latency: 874.106µs message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:20:28Z" - latency: 1.114909ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:19:28Z" - latency: 807.189µs message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:18:28Z" - latency: 1.119861ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:17:28Z" - latency: 948.904µs message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:16:28Z" - latency: 1.073448ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:15:28Z" - latency: 1.747312ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:14:28Z" - latency: 1.420447ms message: 'network-check-target-ip-10-0-128-32: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-network-check-target-ip-10-0-134-47 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "78306" uid: d2466427-b38f-470a-ad49-4fe54f4de44a spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-27T18:40:28Z" message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.686508ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:22:28Z" - latency: 1.928926ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:21:28Z" - latency: 1.711821ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:20:28Z" - latency: 1.975726ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:19:28Z" - latency: 1.745881ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:18:28Z" - latency: 1.750167ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:17:28Z" - latency: 1.909277ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:16:28Z" - latency: 1.928116ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:15:28Z" - latency: 1.982332ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:14:28Z" - latency: 1.798095ms message: 'network-check-target-ip-10-0-134-47: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-27T18:33:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-32-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-32.ec2.internal uid: b169bf51-51ff-40ff-8a7c-c3d1dd296d39 resourceVersion: "88132" uid: fcf6b1c0-4afd-4c5a-8383-041486297c02 spec: sourcePod: network-check-source-7d88cb55d8-f8hjw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-27T18:39:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.044539ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:27:28Z" - latency: 1.414726ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:27:28Z" - latency: 1.934569ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:26:28Z" - latency: 4.350913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:26:28Z" - latency: 1.210269ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:25:28Z" - latency: 1.752891ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:25:28Z" - latency: 843.901µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:24:28Z" - latency: 2.343319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:24:28Z" - latency: 1.110863ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-27T19:23:28Z" - latency: 1.91666ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-27T19:23:28Z" kind: List metadata: resourceVersion: ""