apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "138622" uid: 360f6be5-1cc1-4580-aacf-903920a2bfa6 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T05:54:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.184656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:25:39Z" - latency: 1.228853ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:24:39Z" - latency: 1.314176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:23:39Z" - latency: 859.599µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:22:39Z" - latency: 911.278µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:21:39Z" - latency: 1.574665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:20:39Z" - latency: 1.075033ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:19:39Z" - latency: 958.013µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:18:39Z" - latency: 954.286µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:17:39Z" - latency: 4.354963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "142338" uid: 18a47581-acfa-41ac-83d3-cf8247194c49 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T05:53:39Z" message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.408713ms message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:30:39Z" - latency: 6.951705ms message: 'load-balancer-api-external: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:30:39Z" - latency: 53.849424ms message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:29:39Z" - latency: 6.269094ms message: 'load-balancer-api-external: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:29:39Z" - latency: 52.469883ms message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:28:39Z" - latency: 6.309436ms message: 'load-balancer-api-external: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:28:39Z" - latency: 54.959834ms message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:27:39Z" - latency: 16.483959ms message: 'load-balancer-api-external: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:27:39Z" - latency: 54.004556ms message: 'load-balancer-api-external: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:26:39Z" - latency: 6.664837ms message: 'load-balancer-api-external: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:26:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "142337" uid: 10e4f0eb-e56c-4728-865f-dce47ae83d73 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T05:53:39Z" message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.451151ms message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:30:39Z" - latency: 6.886957ms message: 'load-balancer-api-internal: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:30:39Z" - latency: 53.823539ms message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:29:39Z" - latency: 6.296905ms message: 'load-balancer-api-internal: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:29:39Z" - latency: 3.386816912s message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:28:39Z" - latency: 6.339888ms message: 'load-balancer-api-internal: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:28:39Z" - latency: 54.997715ms message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:27:39Z" - latency: 16.439748ms message: 'load-balancer-api-internal: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:27:39Z" - latency: 54.113915ms message: 'load-balancer-api-internal: tcp connection to a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:26:39Z" - latency: 6.615197ms message: 'load-balancer-api-internal: resolved host name a902e330db8824c50ae5cc9eea4facf0-230a45cd30a76d02.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T07:26:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-network-check-target-ip-10-0-129-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "138621" uid: 89d9f619-eeb7-445c-afeb-526eb9ac5047 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T05:54:39Z" message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.384516ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:25:39Z" - latency: 1.756552ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:24:39Z" - latency: 2.138932ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:23:39Z" - latency: 2.080417ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:22:39Z" - latency: 2.17306ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:21:39Z" - latency: 1.999301ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:20:39Z" - latency: 1.829886ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:19:39Z" - latency: 2.069655ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:18:39Z" - latency: 1.830827ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:17:39Z" - latency: 10.599698ms message: 'network-check-target-ip-10-0-129-213: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-network-check-target-ip-10-0-138-190 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "138620" uid: 6d416021-d2d6-4beb-a6f7-1e2ca29931e7 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T05:54:39Z" message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.099133ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:25:39Z" - latency: 2.280487ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:24:39Z" - latency: 2.318235ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:23:39Z" - latency: 2.365853ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:22:39Z" - latency: 2.295012ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:21:39Z" - latency: 3.219749ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:20:39Z" - latency: 2.130362ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:19:39Z" - latency: 3.266812ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:18:39Z" - latency: 2.254166ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:17:39Z" - latency: 5.548543ms message: 'network-check-target-ip-10-0-138-190: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-network-check-target-ip-10-0-143-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "138619" uid: 2f385329-83f0-4d48-8a85-cc9d5d902f13 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T05:54:39Z" message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.852087ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:25:39Z" - latency: 1.079234ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:24:39Z" - latency: 1.094041ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:23:39Z" - latency: 1.29418ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:22:39Z" - latency: 1.48924ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:21:39Z" - latency: 1.172994ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:20:39Z" - latency: 1.049765ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:19:39Z" - latency: 1.04597ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:18:39Z" - latency: 850.364µs message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:17:39Z" - latency: 10.188435ms message: 'network-check-target-ip-10-0-143-195: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:16:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T05:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-195.us-west-1.compute.internal uid: c1bc2925-6712-4464-afe1-bdc9cc19b480 resourceVersion: "142334" uid: 3cbf41c1-fb91-4a74-abc5-d67d4f78ff67 spec: sourcePod: network-check-source-6f78d59f99-pgxkq targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T05:53:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.69µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:30:39Z" - latency: 2.512848ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:30:39Z" - latency: 841.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:29:39Z" - latency: 1.678995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:29:39Z" - latency: 1.457279ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:28:39Z" - latency: 1.950158ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:28:39Z" - latency: 991.122µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:27:39Z" - latency: 2.73915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:27:39Z" - latency: 1.11137ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T07:26:39Z" - latency: 1.773604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T07:26:39Z" kind: List metadata: resourceVersion: ""