apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "47733" uid: 10148285-591a-463c-b7e6-5a8b36b5d1b9 spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-21T14:38:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.491224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 1.038562ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 919.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 1.306466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 989.466µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:02:17Z" - latency: 1.012179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:01:17Z" - latency: 987.034µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:00:17Z" - latency: 1.865334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:59:17Z" - latency: 963.207µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:58:17Z" - latency: 1.083678ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:57:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "48454" uid: 54c91159-233e-456e-bcea-33bc1413a98d spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T14:37:18Z" message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.301997ms message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:07:17Z" - latency: 6.117142ms message: 'load-balancer-api-external: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:07:17Z" - latency: 9.177606ms message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 8.430615ms message: 'load-balancer-api-external: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:06:17Z" - latency: 5.409958ms message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 5.643872ms message: 'load-balancer-api-external: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:05:17Z" - latency: 4.216497ms message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 10.461308ms message: 'load-balancer-api-external: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:04:17Z" - latency: 5.422748ms message: 'load-balancer-api-external: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 6.889795ms message: 'load-balancer-api-external: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "48455" uid: ad23f581-7c34-4f63-afa5-0c7d6761a565 spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-21T14:37:18Z" message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.313447ms message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:07:17Z" - latency: 6.236854ms message: 'load-balancer-api-internal: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:07:17Z" - latency: 9.809432ms message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 8.488267ms message: 'load-balancer-api-internal: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:06:17Z" - latency: 5.401618ms message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 5.707268ms message: 'load-balancer-api-internal: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:05:17Z" - latency: 4.945362ms message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 10.51248ms message: 'load-balancer-api-internal: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:04:17Z" - latency: 4.742673ms message: 'load-balancer-api-internal: tcp connection to a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 6.912977ms message: 'load-balancer-api-internal: resolved host name a0be2efcfd0564ac38a39b8f64d474bc-7caa1310f31c55cf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-21T15:03:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-network-check-target-ip-10-0-138-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "47732" uid: 44b47611-ecf2-4f6d-9494-a07c6765cecf spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-21T14:38:17Z" message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.302016ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 2.332028ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 2.884124ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 2.462345ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 2.695409ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:02:17Z" - latency: 2.383705ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:01:17Z" - latency: 2.432756ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:00:17Z" - latency: 2.532484ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:59:17Z" - latency: 2.173545ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:58:17Z" - latency: 2.281193ms message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:57:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-network-check-target-ip-10-0-138-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "47730" uid: 472988ee-94aa-4311-bdbe-5aa57a5adc4b spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T14:38:17Z" message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.396544ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 2.430351ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 3.221293ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 2.416767ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 2.310154ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:02:17Z" - latency: 2.577866ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:01:17Z" - latency: 2.435186ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:00:17Z" - latency: 2.516308ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:59:17Z" - latency: 2.410835ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:58:17Z" - latency: 2.524737ms message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:57:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-network-check-target-ip-10-0-141-61 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "47731" uid: 72ee401e-9e51-4977-a9a9-7eb157f7d546 spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-21T14:38:17Z" message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.592075ms message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 955.69µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 908.793µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 931.382µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 976.592µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:02:17Z" - latency: 916.96µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:01:17Z" - latency: 998.977µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:00:17Z" - latency: 913.925µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:59:17Z" - latency: 937.997µs message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:58:17Z" - latency: 1.063918ms message: 'network-check-target-ip-10-0-141-61: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-21T14:57:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-21T14:31:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-61-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-61.ec2.internal uid: cfa98bb6-8a54-489e-9ce9-1c05c41798f2 resourceVersion: "48453" uid: f8bd064e-5ff5-4c66-967d-392bf454ed90 spec: sourcePod: network-check-source-8894fc9bd-jvt2j targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-21T14:37:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.402447ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:07:17Z" - latency: 1.814911ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T15:07:17Z" - latency: 843.058µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:06:17Z" - latency: 1.934057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T15:06:17Z" - latency: 864.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:05:17Z" - latency: 1.61087ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T15:05:17Z" - latency: 1.023872ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:04:17Z" - latency: 2.941227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T15:04:17Z" - latency: 931.615µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-21T15:03:17Z" - latency: 1.669131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-21T15:03:17Z" kind: List metadata: resourceVersion: ""