apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "53612" uid: 2ef62964-6c56-4c3b-a5c4-1ed17d1a12d6 spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 757.857µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.0847ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 1.116228ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.071222ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 962µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 953.755µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 1.032002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 975.568µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 940.442µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 1.138017ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "54490" uid: f3e28fb4-e5b1-4403-8ff8-6aa9ff9e0a6a spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.753953ms message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 6.949046ms message: 'load-balancer-api-external: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 5.135435ms message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 6.729957ms message: 'load-balancer-api-external: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 4.030437ms message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 7.321753ms message: 'load-balancer-api-external: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 4.402226ms message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 6.723894ms message: 'load-balancer-api-external: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 3.593377ms message: 'load-balancer-api-external: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 6.909346ms message: 'load-balancer-api-external: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "54489" uid: 1099dead-e3b9-4b90-9e5b-fb96f4a899af spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.799623ms message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 6.984091ms message: 'load-balancer-api-internal: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 5.109002ms message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 6.782138ms message: 'load-balancer-api-internal: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 4.130502ms message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 7.243393ms message: 'load-balancer-api-internal: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 3.450107ms message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 6.634152ms message: 'load-balancer-api-internal: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 4.729504ms message: 'load-balancer-api-internal: tcp connection to a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 6.813657ms message: 'load-balancer-api-internal: resolved host name a52642e3c591940c580d964ddcba9dca-1d7c487bbfa72d8a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-network-check-target-ip-10-0-128-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "53609" uid: ec799d66-64c4-48e9-9133-326fb6307564 spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 841.883µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 899.862µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 755.684µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.768315ms message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 1.171685ms message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 856.044µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 840.037µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 932.133µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 885.916µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 677.817µs message: 'network-check-target-ip-10-0-128-53: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-network-check-target-ip-10-0-129-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "53610" uid: e2b1bb35-298a-44a5-9353-1c9576fa754c spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.094462ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 2.263685ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 2.347346ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 2.477818ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 2.459426ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 2.458388ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 2.367185ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 2.336922ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 2.230953ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 2.174738ms message: 'network-check-target-ip-10-0-129-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-network-check-target-ip-10-0-143-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "53611" uid: ec655891-8cde-4727-a931-8216142f2d14 spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-05T13:30:07Z" message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.027501ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.900448ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 2.17202ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 2.277746ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 2.344696ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:54:07Z" - latency: 2.079394ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:53:07Z" - latency: 2.719885ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:52:07Z" - latency: 2.137933ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:51:07Z" - latency: 2.118097ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:50:07Z" - latency: 2.354428ms message: 'network-check-target-ip-10-0-143-21: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:49:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-05T13:23:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-53-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-53.ec2.internal uid: 9cd9250e-b88e-4bad-a139-01f808ff98da resourceVersion: "54488" uid: 1d5bc189-eda4-4fdd-95fe-6f10ee753c3a spec: sourcePod: network-check-source-989f8b8dc-cld7t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-05T13:29:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013016ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:59:07Z" - latency: 1.632378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:59:07Z" - latency: 1.031647ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:58:07Z" - latency: 1.81404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:58:07Z" - latency: 1.161354ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:57:07Z" - latency: 1.878257ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:57:07Z" - latency: 854.047µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:56:07Z" - latency: 1.666777ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:56:07Z" - latency: 955.884µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-05T13:55:07Z" - latency: 2.295263ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-05T13:55:07Z" kind: List metadata: resourceVersion: ""