apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113038" uid: 3540374d-ec74-49bc-b407-e96e5923da2e spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:25:41Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 1.300901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 1.123172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 1.076498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 1.268496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:41Z" - latency: 1.137846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:41Z" - latency: 1.27467ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:41Z" - latency: 835.772µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:41Z" - latency: 1.374148ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:41Z" - latency: 1.025673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113557" uid: 2237f810-48ec-4502-b716-9f95a7e66653 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:24:41Z" message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.812046ms message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:41Z" - latency: 6.858815ms message: 'load-balancer-api-external: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:41Z" - latency: 54.002356ms message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 6.302533ms message: 'load-balancer-api-external: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:41Z" - latency: 54.073943ms message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 5.586313ms message: 'load-balancer-api-external: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:41Z" - latency: 53.258521ms message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 4.625988ms message: 'load-balancer-api-external: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:41Z" - latency: 54.025629ms message: 'load-balancer-api-external: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 4.968181ms message: 'load-balancer-api-external: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113558" uid: ca37bb78-0fd9-4952-89db-3f538ba98387 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:24:41Z" message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.891189ms message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:41Z" - latency: 8.201658ms message: 'load-balancer-api-internal: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:41Z" - latency: 54.267348ms message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 8.141192ms message: 'load-balancer-api-internal: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:41Z" - latency: 53.159561ms message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 6.723991ms message: 'load-balancer-api-internal: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:41Z" - latency: 3.385522672s message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 5.897146ms message: 'load-balancer-api-internal: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:41Z" - latency: 3.386719376s message: 'load-balancer-api-internal: tcp connection to a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 6.367048ms message: 'load-balancer-api-internal: resolved host name a307518d15e3f4f029c52010fdce43ee-4fb9e135dd735df7.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-128-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113035" uid: ab49c2db-7d00-4ea9-8f83-729e6700b682 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:25:41Z" message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.787206ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 2.007507ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 1.766846ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 1.91648ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 2.092688ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:41Z" - latency: 1.987974ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:41Z" - latency: 2.031764ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:41Z" - latency: 2.254164ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:41Z" - latency: 2.044189ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:41Z" - latency: 1.990578ms message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-135-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113036" uid: 172dc867-9eff-47d6-8bfb-33d906c34bf6 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:25:41Z" message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 987.141µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 1.176891ms message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 827.075µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 737.839µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 975.623µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:41Z" - latency: 789.341µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:41Z" - latency: 915.6µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:41Z" - latency: 1.395973ms message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:41Z" - latency: 955.551µs message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:41Z" - latency: 1.441009ms message: 'network-check-target-ip-10-0-135-205: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-network-check-target-ip-10-0-142-119 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113037" uid: 3d2b4f40-2e62-4b73-9e36-82b9b760eb80 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:25:41Z" message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.078577ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 2.311162ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 1.936122ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 2.010851ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 2.188489ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:41Z" - latency: 2.299135ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:41Z" - latency: 2.261753ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:41Z" - latency: 2.196493ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:41Z" - latency: 2.092166ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:41Z" - latency: 3.312331ms message: 'network-check-target-ip-10-0-142-119: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:41Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-205.us-west-1.compute.internal uid: f7d8f7ea-f3bb-4eaa-a3c9-78d0aa2088fe resourceVersion: "113555" uid: af9a8dfe-6f27-4b0d-bed1-a92ca0ec0016 spec: sourcePod: network-check-source-6f78d59f99-mddn5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:24:41Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.195µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:41Z" - latency: 1.750815ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:41Z" - latency: 887.985µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:41Z" - latency: 2.042331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:41Z" - latency: 961.459µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:41Z" - latency: 2.011184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:41Z" - latency: 807.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:41Z" - latency: 1.739368ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:41Z" - latency: 965.349µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:41Z" - latency: 1.907006ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:41Z" kind: List metadata: resourceVersion: ""