apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "33380" uid: ae49f87e-782e-48f5-a0eb-dd4ebafeb4d0 spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:00:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.159706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:14:07Z" - latency: 10.020616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:13:07Z" - latency: 1.035534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:12:07Z" - latency: 1.024628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 4.609566ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 1.538206ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 873.653µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 866.452µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 4.362431ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:07Z" - latency: 828.737µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "30519" uid: 70998ed4-c489-441f-b283-f54806107c10 spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:59:07Z" message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.492362ms message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 6.650983ms message: 'load-balancer-api-external: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:11:07Z" - latency: 61.905472ms message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 44.985463ms message: 'load-balancer-api-external: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:10:07Z" - latency: 55.548912ms message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 6.277927ms message: 'load-balancer-api-external: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:09:07Z" - latency: 54.784248ms message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 6.310789ms message: 'load-balancer-api-external: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:08:07Z" - latency: 60.151954ms message: 'load-balancer-api-external: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 6.06588ms message: 'load-balancer-api-external: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "30520" uid: f61f04ec-2604-4603-8232-bbccbb17954d spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T19:59:07Z" message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.481276ms message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 6.745811ms message: 'load-balancer-api-internal: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:11:07Z" - latency: 61.519533ms message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 39.693776ms message: 'load-balancer-api-internal: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:10:07Z" - latency: 55.538265ms message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 6.251287ms message: 'load-balancer-api-internal: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:09:07Z" - latency: 54.797919ms message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 6.341543ms message: 'load-balancer-api-internal: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:08:07Z" - latency: 60.617042ms message: 'load-balancer-api-internal: tcp connection to ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 6.04575ms message: 'load-balancer-api-internal: resolved host name ac5c5bdcb9dd34b2db451ae290864639-b04dcf4e4c158c13.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:07:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-network-check-target-ip-10-0-131-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "33379" uid: cfadb3a9-507a-483d-97ab-dd46a264a406 spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:07Z" message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267728ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:14:07Z" - latency: 8.655285ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:13:07Z" - latency: 2.640675ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:12:07Z" - latency: 2.41942ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 6.693152ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 2.129681ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 1.893623ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 2.705967ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 5.183253ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:07Z" - latency: 2.36347ms message: 'network-check-target-ip-10-0-131-101: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-network-check-target-ip-10-0-131-64 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "33375" uid: 1e665c80-17d8-49a2-90b3-bbc0657d2220 spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:07Z" message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 898.198µs message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:14:07Z" - latency: 29.830841ms message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:13:07Z" - latency: 1.350529ms message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:12:07Z" - latency: 972.712µs message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 13.696057ms message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 1.685941ms message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 893.133µs message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 981.372µs message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 5.567238ms message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:07Z" - latency: 768.367µs message: 'network-check-target-ip-10-0-131-64: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-network-check-target-ip-10-0-134-71 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "33376" uid: f4213975-43b7-437b-a5be-5731c175ae6b spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:00:07Z" message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.045518ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:14:07Z" - latency: 9.824689ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:13:07Z" - latency: 2.192739ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:12:07Z" - latency: 2.577317ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 7.849889ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 2.138875ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 2.265378ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 2.257963ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 4.867791ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:06:07Z" - latency: 2.438119ms message: 'network-check-target-ip-10-0-134-71: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:05:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T19:53:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-64-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-64.us-west-1.compute.internal uid: 18ddebf1-6852-4d1c-b5c8-b3c46330fcb2 resourceVersion: "30517" uid: 7c5cabaa-9d41-4771-bc20-dfc2fc414842 spec: sourcePod: network-check-source-6f78d59f99-shrbz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T19:59:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.614547ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:11:07Z" - latency: 1.777886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:11:07Z" - latency: 3.817027ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:10:07Z" - latency: 19.512529ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:10:07Z" - latency: 890.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:09:07Z" - latency: 1.961293ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:09:07Z" - latency: 829.855µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:08:07Z" - latency: 1.920735ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:08:07Z" - latency: 1.029019ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:07:07Z" - latency: 1.916728ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:07:07Z" kind: List metadata: resourceVersion: ""