apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "46022" uid: 1ec18e50-f11b-48f5-84f6-32973b14930b spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T16:34:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 994.904µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:16:16Z" - latency: 1.068032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 906.462µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 1.59038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 1.009539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 842.745µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 1.248964ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:10:16Z" - latency: 1.132813ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:09:16Z" - latency: 818.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:08:16Z" - latency: 945.896µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "45066" uid: 851b4d4d-1f5d-4fc8-b09b-d32ba696342b spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T16:33:16Z" message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.480605ms message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 7.023927ms message: 'load-balancer-api-external: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:15:16Z" - latency: 5.521355ms message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 6.723159ms message: 'load-balancer-api-external: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:14:16Z" - latency: 6.086595ms message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 7.496417ms message: 'load-balancer-api-external: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:13:16Z" - latency: 3.889105ms message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 6.540601ms message: 'load-balancer-api-external: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:12:16Z" - latency: 4.558272ms message: 'load-balancer-api-external: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 6.700458ms message: 'load-balancer-api-external: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "45067" uid: b6b96eee-8079-42e9-994c-e1718e9da798 spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T16:33:16Z" message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.885861ms message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 6.961243ms message: 'load-balancer-api-internal: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:15:16Z" - latency: 5.511818ms message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 6.755665ms message: 'load-balancer-api-internal: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:14:16Z" - latency: 5.39551ms message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 7.609827ms message: 'load-balancer-api-internal: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:13:16Z" - latency: 3.871626ms message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 6.629867ms message: 'load-balancer-api-internal: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:12:16Z" - latency: 4.555127ms message: 'load-balancer-api-internal: tcp connection to a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 6.745631ms message: 'load-balancer-api-internal: resolved host name a98152178c59d4465a71bd166c5e4836-964bf883e1870a3c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T17:11:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-137-144 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "46020" uid: e2d7bd94-9542-4e7c-89aa-acb2829a0b04 spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T16:34:16Z" message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245817ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:16:16Z" - latency: 2.240753ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 2.270647ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 2.103414ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 2.31892ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 2.054497ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 2.351374ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:10:16Z" - latency: 2.316829ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:09:16Z" - latency: 2.150679ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:08:16Z" - latency: 2.126528ms message: 'network-check-target-ip-10-0-137-144: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-141-251 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "46021" uid: 1e59c7b5-93de-4a15-9176-61dca3ec7376 spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T16:34:16Z" message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.172717ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:16:16Z" - latency: 2.399149ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 2.527139ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 2.142826ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 2.272304ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 1.94024ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 2.097613ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:10:16Z" - latency: 2.290535ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:09:16Z" - latency: 2.093779ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:08:16Z" - latency: 2.049892ms message: 'network-check-target-ip-10-0-141-251: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-network-check-target-ip-10-0-142-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "46019" uid: 9f8b0324-ea1f-4ded-8313-a6880fe76aa6 spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T16:34:16Z" message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 924.074µs message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:16:16Z" - latency: 1.033421ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 1.118973ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 1.172495ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 933.75µs message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 994.424µs message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 922.436µs message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:10:16Z" - latency: 1.232524ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:09:16Z" - latency: 934.954µs message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:08:16Z" - latency: 1.267457ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:07:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T16:27:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-238-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-238.ec2.internal uid: 5dee6a40-28eb-4431-8756-247ffb05fb81 resourceVersion: "45065" uid: 1b5705ae-7729-4c8c-bfdd-faadaadf2dc9 spec: sourcePod: network-check-source-8894fc9bd-lcxgg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T16:33:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.043521ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:15:16Z" - latency: 1.847669ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T17:15:16Z" - latency: 884.789µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:14:16Z" - latency: 2.014692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T17:14:16Z" - latency: 838.703µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:13:16Z" - latency: 2.169344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T17:13:16Z" - latency: 839.501µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:12:16Z" - latency: 2.035692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T17:12:16Z" - latency: 1.02252ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T17:11:16Z" - latency: 1.873978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T17:11:16Z" kind: List metadata: resourceVersion: ""