apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "174104" uid: f8fbfaac-e7f4-4829-8fdb-d5baaea5ec58 spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T14:26:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.379604ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 1.168029ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 937.981µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 1.466718ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:08:22Z" - latency: 1.076586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:07:22Z" - latency: 1.253923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:06:22Z" - latency: 1.336219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:05:22Z" - latency: 1.376773ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:04:22Z" - latency: 1.142635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:03:22Z" - latency: 1.175367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "175669" uid: 99161112-3a4e-41ca-afe5-909ebc59f65f spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T14:25:22Z" message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 61.492302ms message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:13:22Z" - latency: 54.88461ms message: 'load-balancer-api-external: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:13:22Z" - latency: 50.906741ms message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:12:22Z" - latency: 6.196957ms message: 'load-balancer-api-external: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:12:22Z" - latency: 50.015257ms message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 7.069607ms message: 'load-balancer-api-external: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:11:22Z" - latency: 55.51166ms message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 6.78739ms message: 'load-balancer-api-external: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:10:22Z" - latency: 53.492347ms message: 'load-balancer-api-external: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 6.802084ms message: 'load-balancer-api-external: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:09:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "175668" uid: 4c68d440-7ef4-40e0-a8a2-5ed91127eb5e spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T14:25:22Z" message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 62.087837ms message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:13:22Z" - latency: 54.398945ms message: 'load-balancer-api-internal: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:13:22Z" - latency: 54.935436ms message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:12:22Z" - latency: 6.241697ms message: 'load-balancer-api-internal: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:12:22Z" - latency: 50.05977ms message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 7.041243ms message: 'load-balancer-api-internal: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:11:22Z" - latency: 55.506481ms message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 6.747462ms message: 'load-balancer-api-internal: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:10:22Z" - latency: 53.535923ms message: 'load-balancer-api-internal: tcp connection to a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 6.732488ms message: 'load-balancer-api-internal: resolved host name a2ba49ef185a5444dbb27d29e6baf327-c3ad9244eeee9bec.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T16:09:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-131-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "174100" uid: 94f9b34f-22ac-4df2-9131-2862beb33891 spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T14:26:22Z" message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.729074ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 1.590224ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 1.902004ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 2.080179ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:08:22Z" - latency: 2.090931ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:07:22Z" - latency: 2.144036ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:06:22Z" - latency: 1.758376ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:05:22Z" - latency: 1.973545ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:04:22Z" - latency: 1.719619ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:03:22Z" - latency: 1.754619ms message: 'network-check-target-ip-10-0-131-109: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-134-37 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "174101" uid: cd43739a-13c2-4a0f-a7ef-afebfb6a2b9f spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T14:26:22Z" message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.593438ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 1.261049ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 1.024385ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 1.466645ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:08:22Z" - latency: 849.232µs message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:07:22Z" - latency: 898.448µs message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:06:22Z" - latency: 1.759709ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:05:22Z" - latency: 1.378774ms message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:04:22Z" - latency: 983.678µs message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:03:22Z" - latency: 918.746µs message: 'network-check-target-ip-10-0-134-37: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-network-check-target-ip-10-0-135-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "174102" uid: 7d546097-940b-4b04-aed4-a9b72b271696 spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T14:26:22Z" message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.226649ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 2.198347ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 2.012593ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 2.264908ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:08:22Z" - latency: 2.331677ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:07:22Z" - latency: 2.005643ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:06:22Z" - latency: 2.191173ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:05:22Z" - latency: 2.415351ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:04:22Z" - latency: 2.208679ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:03:22Z" - latency: 2.282758ms message: 'network-check-target-ip-10-0-135-142: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:02:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T14:19:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-37-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-37.us-west-2.compute.internal uid: 10217891-49c9-4107-b63b-9f241f23d110 resourceVersion: "175666" uid: f4474f0a-3e7f-401c-857a-c25bad9d5119 spec: sourcePod: network-check-source-6f78d59f99-lhdpr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T14:25:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 11.077593ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:13:22Z" - latency: 6.140108ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T16:13:22Z" - latency: 687.814µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:12:22Z" - latency: 517.374µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T16:12:22Z" - latency: 803.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:11:22Z" - latency: 458.449µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T16:11:22Z" - latency: 792.289µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:10:22Z" - latency: 538.549µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T16:10:22Z" - latency: 837.45µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T16:09:22Z" - latency: 548.543µs message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T16:09:22Z" kind: List metadata: resourceVersion: ""