apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55080" uid: 03665b57-5030-4d0e-b9d2-0793ed40a538 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T23:57:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.105624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 1.040466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 1.285784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 1.278514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 893.629µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:21:05Z" - latency: 1.080586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:20:05Z" - latency: 951.556µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:19:05Z" - latency: 775.686µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:18:05Z" - latency: 1.253283ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:17:05Z" - latency: 829.638µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55985" uid: 07bbd460-247a-4b94-abdb-24df2e48e463 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T23:56:05Z" message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.982406ms message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:26:05Z" - latency: 8.018741ms message: 'load-balancer-api-external: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:26:05Z" - latency: 5.142831ms message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 6.983031ms message: 'load-balancer-api-external: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:25:05Z" - latency: 5.02924ms message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 8.678674ms message: 'load-balancer-api-external: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:24:05Z" - latency: 4.234161ms message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 8.922346ms message: 'load-balancer-api-external: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:23:05Z" - latency: 5.48414ms message: 'load-balancer-api-external: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 8.465356ms message: 'load-balancer-api-external: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:22:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55986" uid: 0413293b-2f54-4cbe-902a-da2859545cfd spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T23:56:05Z" message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.005628ms message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:26:05Z" - latency: 7.937742ms message: 'load-balancer-api-internal: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:26:05Z" - latency: 8.604217ms message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 7.059705ms message: 'load-balancer-api-internal: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:25:05Z" - latency: 5.049844ms message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 8.618885ms message: 'load-balancer-api-internal: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:24:05Z" - latency: 5.576602ms message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 9.006678ms message: 'load-balancer-api-internal: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:23:05Z" - latency: 5.475433ms message: 'load-balancer-api-internal: tcp connection to aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 8.561221ms message: 'load-balancer-api-internal: resolved host name aab1237b2159446e0899a470bae7d7b7-4cca1118994de334.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-16T00:22:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-network-check-target-ip-10-0-129-211 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55077" uid: e665580f-97d4-44a1-897a-42a52e2bbda9 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T23:57:05Z" message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.312417ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 1.785937ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 1.786982ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 1.87087ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 1.568163ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:21:05Z" - latency: 1.921531ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:20:05Z" - latency: 2.038413ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:19:05Z" - latency: 1.844477ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:18:05Z" - latency: 2.060789ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:17:05Z" - latency: 1.813888ms message: 'network-check-target-ip-10-0-129-211: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-network-check-target-ip-10-0-140-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55079" uid: 9bc32487-3534-47d8-947d-90b4d3876082 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T23:57:05Z" message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.481325ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 2.588685ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 2.377149ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 2.478098ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 2.093428ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:21:05Z" - latency: 2.402375ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:20:05Z" - latency: 2.319457ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:19:05Z" - latency: 2.114005ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:18:05Z" - latency: 2.388865ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:17:05Z" - latency: 1.994493ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-network-check-target-ip-10-0-142-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55078" uid: 55a90502-9f92-4dbe-adc4-9f26d1c99961 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T23:57:05Z" message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.525651ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 948.044µs message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 1.053511ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 1.081613ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 957.788µs message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:21:05Z" - latency: 983.343µs message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:20:05Z" - latency: 1.215683ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:19:05Z" - latency: 1.077179ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:18:05Z" - latency: 996.798µs message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:17:05Z" - latency: 1.070552ms message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:16:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T23:50:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-228-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-228.ec2.internal uid: 74456c35-dc8c-4190-b744-d5d0e24518ae resourceVersion: "55984" uid: dfca0b1e-fbaf-46e6-8f0f-3e970e6dd9c0 spec: sourcePod: network-check-source-869dcfcdcd-fmsfn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T23:56:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.311988ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:26:05Z" - latency: 1.830711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T00:26:05Z" - latency: 907.62µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:25:05Z" - latency: 1.676903ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T00:25:05Z" - latency: 855.41µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:24:05Z" - latency: 1.918131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T00:24:05Z" - latency: 797.189µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:23:05Z" - latency: 1.943984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T00:23:05Z" - latency: 826.151µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-16T00:22:05Z" - latency: 1.957867ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-16T00:22:05Z" kind: List metadata: resourceVersion: ""