apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "71785" uid: 47f2a4ac-c2ac-4c3f-9f75-20c90600ffc2 spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-29T19:14:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.810146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:56:19Z" - latency: 826.891µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 1.352943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 1.103856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 785.143µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 1.2696ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 857.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:50:19Z" - latency: 1.180627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:49:19Z" - latency: 663.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:48:19Z" - latency: 1.115019ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "70894" uid: 496cbc1b-035e-42b4-a242-6b2d8b6b76b6 spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:13:19Z" message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.317392ms message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 8.63915ms message: 'load-balancer-api-external: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:55:19Z" - latency: 3.709467ms message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 7.268364ms message: 'load-balancer-api-external: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:54:19Z" - latency: 5.127464ms message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 6.956607ms message: 'load-balancer-api-external: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:53:19Z" - latency: 4.196492ms message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 12.302075ms message: 'load-balancer-api-external: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:52:19Z" - latency: 4.461801ms message: 'load-balancer-api-external: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 7.356246ms message: 'load-balancer-api-external: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:51:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "70895" uid: 7614069d-0185-4697-81e8-08376a40608f spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-29T19:13:19Z" message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.271201ms message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 8.613485ms message: 'load-balancer-api-internal: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:55:19Z" - latency: 3.658837ms message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 7.208191ms message: 'load-balancer-api-internal: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:54:19Z" - latency: 5.129809ms message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 6.912448ms message: 'load-balancer-api-internal: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:53:19Z" - latency: 4.178569ms message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 12.225755ms message: 'load-balancer-api-internal: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:52:19Z" - latency: 4.547159ms message: 'load-balancer-api-internal: tcp connection to a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 7.331832ms message: 'load-balancer-api-internal: resolved host name a905da1c16bb64da89615e48c6a0b9f9-680c98d39354c7a9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-29T19:51:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-130-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "71784" uid: a7882ea9-01ee-41a3-8253-65cb9c8f9596 spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:14:19Z" message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.242191ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:56:19Z" - latency: 1.822671ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 1.983696ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 2.074326ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 2.048803ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 2.108197ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 1.9358ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:50:19Z" - latency: 1.883462ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:49:19Z" - latency: 1.915003ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:48:19Z" - latency: 2.041294ms message: 'network-check-target-ip-10-0-130-75: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-135-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "71783" uid: a0094900-b028-4caf-8e16-5ed159138992 spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:14:19Z" message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.189603ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:56:19Z" - latency: 1.940129ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 2.18039ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 2.202135ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 1.908355ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 2.041746ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 1.844576ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:50:19Z" - latency: 2.162378ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:49:19Z" - latency: 1.796116ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:48:19Z" - latency: 2.130958ms message: 'network-check-target-ip-10-0-135-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-ip-10-0-142-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "71782" uid: bb1b9423-9a65-4798-ac77-53695bb011b9 spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-29T19:14:19Z" message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.222µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:56:19Z" - latency: 962.118µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 1.000116ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 872.541µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 836.174µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 1.271046ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 999.695µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:50:19Z" - latency: 1.102974ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:49:19Z" - latency: 862.622µs message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:48:19Z" - latency: 1.021438ms message: 'network-check-target-ip-10-0-142-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:47:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-29T19:07:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-16.ec2.internal uid: b3f9fdd1-9b4e-4b68-b7cd-89a9f4299589 resourceVersion: "70893" uid: f9a37a39-75fa-4cbe-9111-1d5b391ae52a spec: sourcePod: network-check-source-7d88cb55d8-b27q9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-29T19:13:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.179825ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:55:19Z" - latency: 1.940177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:55:19Z" - latency: 881.728µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:54:19Z" - latency: 1.941448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:54:19Z" - latency: 1.018982ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:53:19Z" - latency: 1.769125ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:53:19Z" - latency: 993.687µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:52:19Z" - latency: 1.816824ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:52:19Z" - latency: 974.808µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-29T19:51:19Z" - latency: 1.86471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-29T19:51:19Z" kind: List metadata: resourceVersion: ""