apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "143372" uid: 9f74f21f-3135-4661-ae2a-ef1fb177a031 spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T12:06:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.159598ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 788.226µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 789.549µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 1.018824ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 1.283559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:20Z" - latency: 1.227683ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:20Z" - latency: 862.804µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:20Z" - latency: 845.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:20Z" - latency: 943.613µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:20Z" - latency: 1.124123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:49:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "144144" uid: 1904e183-fde9-464d-b1ca-f95378201c6f spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:05:21Z" message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.64508ms message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:20Z" - latency: 7.845997ms message: 'load-balancer-api-external: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:59:20Z" - latency: 54.145623ms message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 7.426996ms message: 'load-balancer-api-external: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:20Z" - latency: 53.302415ms message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 6.549719ms message: 'load-balancer-api-external: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:20Z" - latency: 52.201378ms message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 6.578626ms message: 'load-balancer-api-external: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:20Z" - latency: 54.774176ms message: 'load-balancer-api-external: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 6.704463ms message: 'load-balancer-api-external: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "144145" uid: 4510d448-8bcc-45b0-983a-9120cd5cc2da spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T12:05:21Z" message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.60832ms message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:20Z" - latency: 7.893572ms message: 'load-balancer-api-internal: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:59:20Z" - latency: 54.150748ms message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 7.481822ms message: 'load-balancer-api-internal: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:20Z" - latency: 53.312056ms message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 6.519562ms message: 'load-balancer-api-internal: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:20Z" - latency: 52.163244ms message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 6.623108ms message: 'load-balancer-api-internal: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:20Z" - latency: 54.729877ms message: 'load-balancer-api-internal: tcp connection to aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 6.770371ms message: 'load-balancer-api-internal: resolved host name aadda5a39e08548bea3cd7c71322c295-74c64663e2d0aa4a.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-133-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "143370" uid: e4cc600b-a34b-46f1-8542-ea980e87ca9f spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:06:20Z" message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.531491ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 2.369606ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 2.383776ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 2.408904ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 2.6699ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:20Z" - latency: 2.238356ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:20Z" - latency: 2.057469ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:20Z" - latency: 2.20748ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:20Z" - latency: 2.538461ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:20Z" - latency: 2.310055ms message: 'network-check-target-ip-10-0-133-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:49:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-135-24 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "143368" uid: 8545391f-ebad-4786-aa28-7159cc620374 spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:06:20Z" message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.975µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 971.605µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 1.260747ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 1.05599ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 1.541401ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:20Z" - latency: 774.886µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:20Z" - latency: 883.28µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:20Z" - latency: 1.294973ms message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:20Z" - latency: 964.124µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:20Z" - latency: 944.027µs message: 'network-check-target-ip-10-0-135-24: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:49:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-ip-10-0-141-170 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "143369" uid: 098e2305-3343-474c-bc40-287e203056f4 spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T12:06:20Z" message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.352372ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 2.320014ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 2.444735ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 2.42416ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 2.466699ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:54:20Z" - latency: 2.128268ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:53:20Z" - latency: 2.141803ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:52:20Z" - latency: 2.443814ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:51:20Z" - latency: 2.467471ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:50:20Z" - latency: 1.941386ms message: 'network-check-target-ip-10-0-141-170: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:49:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T11:59:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-24-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-24.us-west-1.compute.internal uid: 137cdbc7-0bff-4746-87d9-dbd07fc601d5 resourceVersion: "144142" uid: e4607c21-0754-4f2f-8577-23ad86b58574 spec: sourcePod: network-check-source-6f78d59f99-g7gnd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T12:05:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.036192ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:59:20Z" - latency: 1.541656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:59:20Z" - latency: 855.406µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:58:20Z" - latency: 2.970557ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:58:20Z" - latency: 1.080113ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:57:20Z" - latency: 2.093387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:57:20Z" - latency: 1.026588ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:56:20Z" - latency: 1.843613ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:56:20Z" - latency: 924.819µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T13:55:20Z" - latency: 1.689857ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T13:55:20Z" kind: List metadata: resourceVersion: ""