apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "42720" uid: 6a360472-8989-49e7-b7c6-3eff5c7c7e79 spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-10T13:13:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.483372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:34:11Z" - latency: 943.705µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:33:11Z" - latency: 920.68µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:32:11Z" - latency: 935.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:31:11Z" - latency: 1.15855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 1.116372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 1.060334ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 1.725381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 1.318325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 1.162966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "38953" uid: a5304b49-bcf8-4e90-ab8e-7f78fba9b90b spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:12:11Z" message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.75874ms message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 6.873469ms message: 'load-balancer-api-external: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:30:11Z" - latency: 5.21902ms message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 8.285638ms message: 'load-balancer-api-external: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:29:11Z" - latency: 5.158198ms message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 8.046068ms message: 'load-balancer-api-external: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:28:11Z" - latency: 6.095388ms message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 9.52798ms message: 'load-balancer-api-external: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:27:11Z" - latency: 3.336131ms message: 'load-balancer-api-external: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 6.688475ms message: 'load-balancer-api-external: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "38954" uid: 27b90f46-5495-4a3b-b903-9ac4c8dfdf0e spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-10T13:12:11Z" message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.914339ms message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 6.934698ms message: 'load-balancer-api-internal: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:30:11Z" - latency: 5.186447ms message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 8.310869ms message: 'load-balancer-api-internal: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:29:11Z" - latency: 5.627594ms message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 8.163347ms message: 'load-balancer-api-internal: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:28:11Z" - latency: 6.123672ms message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 9.55757ms message: 'load-balancer-api-internal: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:27:11Z" - latency: 3.263444ms message: 'load-balancer-api-internal: tcp connection to a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 6.774522ms message: 'load-balancer-api-internal: resolved host name a9229f95565714c848577f84ee80790f-1bf45487d654c487.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-135-143 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "42717" uid: eeb70406-e2f5-423e-b518-931817b06a63 spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:13:11Z" message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.298239ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:34:11Z" - latency: 839.819µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:33:11Z" - latency: 1.106907ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:32:11Z" - latency: 762.123µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:31:11Z" - latency: 787.321µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 955.016µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 813.104µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 1.173935ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 1.495178ms message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 840.991µs message: 'network-check-target-ip-10-0-135-143: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-138-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "42718" uid: 446e297d-937a-40e7-988e-5f7b06f218fa spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:13:11Z" message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.357744ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:34:11Z" - latency: 2.003931ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:33:11Z" - latency: 2.096858ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:32:11Z" - latency: 1.967018ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:31:11Z" - latency: 2.014126ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 1.702285ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 1.973172ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 2.106111ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 2.186906ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 1.809042ms message: 'network-check-target-ip-10-0-138-87: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-network-check-target-ip-10-0-143-131 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "42719" uid: e4e29e39-7f8c-45e8-ac57-5866f92359f1 spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-10T13:13:11Z" message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.945534ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:34:11Z" - latency: 1.89005ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:33:11Z" - latency: 1.975958ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:32:11Z" - latency: 1.792125ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:31:11Z" - latency: 2.020529ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 1.833465ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 1.809709ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 2.166316ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 1.858279ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 2.092676ms message: 'network-check-target-ip-10-0-143-131: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:25:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-10T13:06:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-143-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-143.ec2.internal uid: befd6afd-94f3-4e30-8b5f-1ae1075307b8 resourceVersion: "38952" uid: 0825ecc7-81b2-447c-b6f2-c548742b4d0f spec: sourcePod: network-check-source-dbd9cf844-57qkc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-10T13:12:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.374µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:30:11Z" - latency: 1.904111ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:30:11Z" - latency: 868.634µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:29:11Z" - latency: 1.841252ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:29:11Z" - latency: 857.642µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:28:11Z" - latency: 1.651621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:28:11Z" - latency: 935.482µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:27:11Z" - latency: 2.354433ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:27:11Z" - latency: 1.113853ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T13:26:11Z" - latency: 1.778691ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T13:26:11Z" kind: List metadata: resourceVersion: ""