apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "44238" uid: 540c7393-4631-4c0c-be91-6b9ee736aa1f spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T17:45:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.382845ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 790.525µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 724.574µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 728.766µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:03:22Z" - latency: 990.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:02:22Z" - latency: 1.025614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:01:22Z" - latency: 1.117054ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:00:22Z" - latency: 933.508µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:59:22Z" - latency: 988.721µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:58:22Z" - latency: 1.001359ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "46190" uid: f50e6a44-7360-47a3-9f29-8399e3c03b4f spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T17:44:22Z" message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.314142ms message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:08:22Z" - latency: 6.376333ms message: 'load-balancer-api-external: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:08:22Z" - latency: 4.746462ms message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:07:22Z" - latency: 6.560776ms message: 'load-balancer-api-external: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:07:22Z" - latency: 5.289378ms message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 7.337381ms message: 'load-balancer-api-external: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:06:22Z" - latency: 5.468269ms message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 7.017441ms message: 'load-balancer-api-external: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:05:22Z" - latency: 4.271877ms message: 'load-balancer-api-external: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 5.964123ms message: 'load-balancer-api-external: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:04:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "46189" uid: cbd9b8fd-f8e2-4eda-8595-9cdba557abf2 spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T17:44:22Z" message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.341544ms message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:08:22Z" - latency: 6.268413ms message: 'load-balancer-api-internal: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:08:22Z" - latency: 4.112564ms message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:07:22Z" - latency: 6.620427ms message: 'load-balancer-api-internal: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:07:22Z" - latency: 5.490784ms message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 7.239558ms message: 'load-balancer-api-internal: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:06:22Z" - latency: 5.163439ms message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 7.063653ms message: 'load-balancer-api-internal: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:05:22Z" - latency: 3.641766ms message: 'load-balancer-api-internal: tcp connection to a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 5.864305ms message: 'load-balancer-api-internal: resolved host name a99536ce488044ba3b8eb3a455deea77-000c00e07de67025.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T18:04:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-network-check-target-ip-10-0-130-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "44236" uid: 4dee5ff0-8907-47a0-887f-0242588d65e7 spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-21T17:45:22Z" message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.036918ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 2.080139ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 2.01495ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 1.844767ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:03:22Z" - latency: 2.162386ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:02:22Z" - latency: 2.311867ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:01:22Z" - latency: 2.186409ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:00:22Z" - latency: 2.756522ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:59:22Z" - latency: 2.236069ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:58:22Z" - latency: 1.987048ms message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-network-check-target-ip-10-0-139-73 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "44237" uid: 78753e64-8af6-464a-81ee-9da6dc6ea4d8 spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T17:45:22Z" message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.138244ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 2.036793ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 2.077868ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 1.819726ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:03:22Z" - latency: 2.176214ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:02:22Z" - latency: 2.058354ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:01:22Z" - latency: 2.082243ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:00:22Z" - latency: 2.717678ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:59:22Z" - latency: 2.03666ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:58:22Z" - latency: 2.113853ms message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-network-check-target-ip-10-0-140-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "44235" uid: 436b3987-0ef0-42dc-94e2-cd45c107c9f3 spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-21T17:45:22Z" message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.702848ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 739.267µs message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 1.074411ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 1.291923ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:03:22Z" - latency: 1.420956ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:02:22Z" - latency: 858.194µs message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:01:22Z" - latency: 904.326µs message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:00:22Z" - latency: 1.367177ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:59:22Z" - latency: 1.154617ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:58:22Z" - latency: 1.39786ms message: 'network-check-target-ip-10-0-140-106: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T17:57:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T17:38:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-106-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-106.ec2.internal uid: 48108ea9-6b81-4bef-80fb-71c694438f17 resourceVersion: "46187" uid: b1977ca3-c938-45c7-95b1-8b5b282088a1 spec: sourcePod: network-check-source-7f44b6dd87-w2lvc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T17:44:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.057923ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:08:22Z" - latency: 1.709091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:08:22Z" - latency: 842.111µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:07:22Z" - latency: 1.762454ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:07:22Z" - latency: 783.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:06:22Z" - latency: 1.777856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:06:22Z" - latency: 920.838µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:05:22Z" - latency: 2.103089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:05:22Z" - latency: 871.611µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T18:04:22Z" - latency: 1.651432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T18:04:22Z" kind: List metadata: resourceVersion: ""