apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "37846" uid: 6a3e21bd-6b69-41bf-9f3c-476d1cf291fb spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T18:12:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:26:29Z" - latency: 1.208369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:25:29Z" - latency: 843.615µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:24:29Z" - latency: 1.003972ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 1.127935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 1.37892ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 1.358213ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 938.663µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 1.246112ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:18:29Z" - latency: 1.06023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "35684" uid: b7223d93-3113-469e-86fd-52f6a9461218 spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:11:29Z" message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.347634ms message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 8.507195ms message: 'load-balancer-api-external: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:23:29Z" - latency: 3.267003ms message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 8.982907ms message: 'load-balancer-api-external: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:22:29Z" - latency: 5.50245ms message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 8.919462ms message: 'load-balancer-api-external: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:21:29Z" - latency: 5.164665ms message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 8.967752ms message: 'load-balancer-api-external: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:20:29Z" - latency: 5.480757ms message: 'load-balancer-api-external: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 8.772802ms message: 'load-balancer-api-external: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "35683" uid: 4ac157b8-a64a-43cc-aabd-7c0d892895ae spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:11:29Z" message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.321967ms message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 8.478384ms message: 'load-balancer-api-internal: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:23:29Z" - latency: 3.149927ms message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 8.970041ms message: 'load-balancer-api-internal: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:22:29Z" - latency: 5.465451ms message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 8.978959ms message: 'load-balancer-api-internal: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:21:29Z" - latency: 5.170337ms message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 8.944375ms message: 'load-balancer-api-internal: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:20:29Z" - latency: 5.453975ms message: 'load-balancer-api-internal: tcp connection to a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 8.847831ms message: 'load-balancer-api-internal: resolved host name a6f99bbb9579f4c26bef2b8a420a6370-421fe37309e29d39.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-128-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "37844" uid: 64007b85-fd51-470f-8b28-a62e575123b4 spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:12:29Z" message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.496834ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:26:29Z" - latency: 2.3145ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:25:29Z" - latency: 2.308918ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:24:29Z" - latency: 2.462709ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 2.16996ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 2.278899ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 2.469775ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 2.616617ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 2.345346ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:18:29Z" - latency: 2.22544ms message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-135-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "37843" uid: 2828f83a-56e7-4be4-b1d4-accafb1d175e spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:12:29Z" message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.026008ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:26:29Z" - latency: 1.121559ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:25:29Z" - latency: 894.89µs message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:24:29Z" - latency: 1.384962ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 958.714µs message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 1.539163ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 876.483µs message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 998.443µs message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 1.702888ms message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:18:29Z" - latency: 891.314µs message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-143-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "37845" uid: 06e2cac5-48c9-4c5f-bc63-73463d7ee350 spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:12:29Z" message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.53864ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:26:29Z" - latency: 2.334855ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:25:29Z" - latency: 2.402417ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:24:29Z" - latency: 2.640331ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 2.349705ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 2.602671ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 2.700212ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 2.064442ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 2.308258ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:18:29Z" - latency: 2.701726ms message: 'network-check-target-ip-10-0-143-15: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:17:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:05:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-97-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-97.ec2.internal uid: d0ddb86b-23c7-4018-87cc-00042bc18233 resourceVersion: "35682" uid: 62e50416-fcb6-47c6-950e-e38fde813317 spec: sourcePod: network-check-source-869dcfcdcd-r999t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T18:11:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 792.958µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:23:29Z" - latency: 1.998461ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:23:29Z" - latency: 1.208926ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:22:29Z" - latency: 1.858655ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:22:29Z" - latency: 836.121µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:21:29Z" - latency: 1.879288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:21:29Z" - latency: 965.592µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:20:29Z" - latency: 2.293303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:20:29Z" - latency: 931.21µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:19:29Z" - latency: 1.83213ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:19:29Z" kind: List metadata: resourceVersion: ""