apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "129815" uid: 4860dc2f-03a5-4ebf-9da3-bc342cf882ef spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T01:05:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:54Z" - latency: 1.100745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:54Z" - latency: 1.385044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:54Z" - latency: 1.226071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:54Z" - latency: 1.929108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:54Z" - latency: 1.594753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 1.057409ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 1.003118ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 1.141095ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 1.255378ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "123369" uid: 7fec1a76-97cf-4428-8a02-736e2bf246ca spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T01:04:54Z" message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.384029ms message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 27.385308ms message: 'load-balancer-api-external: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:10:54Z" - latency: 54.602464ms message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 8.121687ms message: 'load-balancer-api-external: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:09:54Z" - latency: 53.715378ms message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 8.304175ms message: 'load-balancer-api-external: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:08:54Z" - latency: 3.385320939s message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 7.140271ms message: 'load-balancer-api-external: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:07:54Z" - latency: 54.283764ms message: 'load-balancer-api-external: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - latency: 6.767629ms message: 'load-balancer-api-external: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "123370" uid: 920163dc-33ac-4d32-a995-5fa40d9509f6 spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T01:04:54Z" message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.2845ms message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 27.573453ms message: 'load-balancer-api-internal: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:10:54Z" - latency: 53.054033ms message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 8.020446ms message: 'load-balancer-api-internal: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:09:54Z" - latency: 53.710558ms message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 8.190159ms message: 'load-balancer-api-internal: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:08:54Z" - latency: 53.205161ms message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 7.180121ms message: 'load-balancer-api-internal: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:07:54Z" - latency: 54.333074ms message: 'load-balancer-api-internal: tcp connection to a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - latency: 6.584253ms message: 'load-balancer-api-internal: resolved host name a747793b6d5cd47a4aa82ac69821d294-e9c03ac64371c6c0.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-network-check-target-ip-10-0-132-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "129808" uid: 1be1e5ee-00c6-4557-890e-b4c4b2106e91 spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:05:54Z" message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.142124ms message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:54Z" - latency: 918.532µs message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:54Z" - latency: 1.495083ms message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:54Z" - latency: 942.165µs message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:54Z" - latency: 935.002µs message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:54Z" - latency: 2.40115ms message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 1.144035ms message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 947.879µs message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 885.25µs message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 1.90014ms message: 'network-check-target-ip-10-0-132-177: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-network-check-target-ip-10-0-136-249 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "129812" uid: 5fd9c96f-9498-4377-ac10-59c8c3fb8202 spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:05:54Z" message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.079628ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:54Z" - latency: 1.919273ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:54Z" - latency: 2.658899ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:54Z" - latency: 2.278665ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:54Z" - latency: 2.376699ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:54Z" - latency: 2.612465ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 2.251952ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 3.066504ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 2.412258ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 2.304236ms message: 'network-check-target-ip-10-0-136-249: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-network-check-target-ip-10-0-139-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "129809" uid: 19c389d5-882e-4f3e-bb39-4cb0b065f4ee spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-31T01:05:54Z" message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.03661ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:15:54Z" - latency: 2.278781ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:14:54Z" - latency: 2.22704ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:13:54Z" - latency: 1.947231ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:12:54Z" - latency: 2.893507ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:11:54Z" - latency: 2.756678ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 2.708604ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 2.59932ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 2.497211ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 2.118445ms message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:58:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-177-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-177.us-west-1.compute.internal uid: fc68d6ad-169e-441c-8b33-e3cfdec0b1cc resourceVersion: "123352" uid: 3fa4d057-6b55-46d7-9927-02f6f0249339 spec: sourcePod: network-check-source-6f78d59f99-b8xlg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T01:04:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.167859ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:10:54Z" - latency: 3.251162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:10:54Z" - latency: 1.030332ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:09:54Z" - latency: 2.533831ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:09:54Z" - latency: 981.723µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:08:54Z" - latency: 2.221442ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:08:54Z" - latency: 1.138679ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:07:54Z" - latency: 2.297234ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:07:54Z" - latency: 2.17636ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T02:06:54Z" - latency: 1.90049ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T02:06:54Z" kind: List metadata: resourceVersion: ""