apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "33368" uid: dad4d9da-5e63-4f90-ab78-dc2fe9dadba3 spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T22:03:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 1.066415ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:32Z" - latency: 851.615µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:32Z" - latency: 1.278197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:32Z" - latency: 925.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:32Z" - latency: 972.295µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:32Z" - latency: 1.189868ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:32Z" - latency: 853.407µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:32Z" - latency: 1.038184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:32Z" - latency: 942.106µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "35786" uid: 406f9f12-4afa-4620-b69c-d25539c07b8a spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:02:32Z" message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.436704ms message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:32Z" - latency: 8.335464ms message: 'load-balancer-api-external: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:32Z" - latency: 52.409172ms message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:32Z" - latency: 7.847436ms message: 'load-balancer-api-external: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:32Z" - latency: 53.817355ms message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:32Z" - latency: 7.50447ms message: 'load-balancer-api-external: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:32Z" - latency: 55.174834ms message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:32Z" - latency: 7.484854ms message: 'load-balancer-api-external: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:32Z" - latency: 55.891067ms message: 'load-balancer-api-external: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 8.303187ms message: 'load-balancer-api-external: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "35787" uid: cfdf8596-be2b-483d-bbc6-1da51af26f1a spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T22:02:32Z" message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.478778ms message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:32Z" - latency: 8.283346ms message: 'load-balancer-api-internal: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:32Z" - latency: 53.269431ms message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:32Z" - latency: 7.887215ms message: 'load-balancer-api-internal: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:32Z" - latency: 53.847704ms message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:32Z" - latency: 7.555658ms message: 'load-balancer-api-internal: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:32Z" - latency: 55.149569ms message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:32Z" - latency: 7.511686ms message: 'load-balancer-api-internal: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:32Z" - latency: 55.923012ms message: 'load-balancer-api-internal: tcp connection to a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 8.318246ms message: 'load-balancer-api-internal: resolved host name a9adc942bda134c9d9d9f5a2e264780f-d8cf5ed739e19940.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-130-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "33367" uid: 1fb8faae-7d65-4413-b56b-e82b090f5e5e spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:03:32Z" message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.393756ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 2.379305ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:32Z" - latency: 2.38349ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:32Z" - latency: 2.270281ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:32Z" - latency: 3.006042ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:32Z" - latency: 2.136071ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:32Z" - latency: 2.274397ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:32Z" - latency: 2.006244ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:32Z" - latency: 2.451716ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:32Z" - latency: 2.393142ms message: 'network-check-target-ip-10-0-130-162: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-131-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "33366" uid: bd2c4b10-de77-4c53-a0cb-48aee6613482 spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:03:32Z" message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.232591ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 2.420601ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:32Z" - latency: 2.267876ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:32Z" - latency: 2.165955ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:32Z" - latency: 2.492908ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:32Z" - latency: 2.169638ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:32Z" - latency: 2.216962ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:32Z" - latency: 1.922553ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:32Z" - latency: 2.387644ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:32Z" - latency: 2.305043ms message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-ip-10-0-135-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "33365" uid: e6595a9e-4d42-4011-a355-33ee06f2368d spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T22:03:32Z" message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 821.828µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 1.344112ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:32Z" - latency: 722.51µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:32Z" - latency: 929.927µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:32Z" - latency: 827.144µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:48:32Z" - latency: 1.319408ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:47:32Z" - latency: 1.293764ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:46:32Z" - latency: 856.852µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:45:32Z" - latency: 915.221µs message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:44:32Z" - latency: 1.359733ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:43:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:56:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-218-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-218.us-west-1.compute.internal uid: 0599e9f4-b344-4c08-803a-3cfd2c6f7f85 resourceVersion: "35750" uid: 3a3fc9d6-7317-4d3a-8d52-2cd570d8c413 spec: sourcePod: network-check-source-6f78d59f99-p4cgf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T22:02:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 965.022µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:32Z" - latency: 1.671622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:56:32Z" - latency: 915.7µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:32Z" - latency: 1.723487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:55:32Z" - latency: 1.532002ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:32Z" - latency: 1.738055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:32Z" - latency: 806.382µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:32Z" - latency: 1.885146ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:32Z" - latency: 1.109766ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:32Z" - latency: 1.974304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:32Z" kind: List metadata: resourceVersion: ""