apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "21922" uid: e1b68902-5b12-4dd7-bcc8-35bd7123afab spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T17:27: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.343867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:41:22Z" - latency: 1.801164ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:40:22Z" - latency: 1.338815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:39:22Z" - latency: 1.369881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 1.017846ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 1.254732ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 1.299791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 1.668651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 940.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:33:22Z" - latency: 1.263739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "20587" uid: b1367a91-e06e-450c-b867-bf9d526b6289 spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:26:22Z" message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.812012ms message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 7.785651ms message: 'load-balancer-api-external: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:38:22Z" - latency: 5.3726ms message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 8.069166ms message: 'load-balancer-api-external: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:37:22Z" - latency: 6.307055ms message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 6.676361ms message: 'load-balancer-api-external: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:36:22Z" - latency: 6.013968ms message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 6.644798ms message: 'load-balancer-api-external: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:35:22Z" - latency: 7.189977ms message: 'load-balancer-api-external: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 6.902252ms message: 'load-balancer-api-external: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:34:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "20588" uid: 6fa80378-f0bf-4e6b-844a-64f127070371 spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:26:22Z" message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.847952ms message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 7.725002ms message: 'load-balancer-api-internal: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:38:22Z" - latency: 5.366067ms message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 8.146906ms message: 'load-balancer-api-internal: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:37:22Z" - latency: 6.151647ms message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 6.585432ms message: 'load-balancer-api-internal: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:36:22Z" - latency: 5.861016ms message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 6.697225ms message: 'load-balancer-api-internal: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:35:22Z" - latency: 7.231822ms message: 'load-balancer-api-internal: tcp connection to a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 6.782221ms message: 'load-balancer-api-internal: resolved host name a121e6255927a44b4981e24ebcec6824-ae3ad63f07632162.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:34:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-138-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "21919" uid: 34ce4f78-d68b-49ac-ac79-840753abad15 spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:27:22Z" message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.566269ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:41:22Z" - latency: 855.116µs message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:40:22Z" - latency: 1.050398ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:39:22Z" - latency: 1.065766ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 1.142036ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 1.095732ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 1.048022ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 1.170649ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 1.048679ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:33:22Z" - latency: 937.788µs message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-141-36 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "21921" uid: 46f71b58-429f-4e42-ab16-c49b8e4f4479 spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:27:22Z" message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.319965ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:41:22Z" - latency: 2.291898ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:40:22Z" - latency: 2.143057ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:39:22Z" - latency: 2.332769ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 2.18482ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 2.163411ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 2.291956ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 2.326335ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 2.089463ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:33:22Z" - latency: 2.250076ms message: 'network-check-target-ip-10-0-141-36: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-ip-10-0-142-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "21920" uid: 0d691008-f69e-452b-bb31-30869ca12950 spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:27:22Z" message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.465684ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:41:22Z" - latency: 2.271771ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:40:22Z" - latency: 5.47011ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:39:22Z" - latency: 2.410706ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 2.162008ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 2.582801ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 2.767803ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 2.961377ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 2.419374ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:33:22Z" - latency: 2.66182ms message: 'network-check-target-ip-10-0-142-81: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:20:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-97-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-97.ec2.internal uid: b12aa52f-34c5-4f50-b73f-2c7e850af752 resourceVersion: "20586" uid: 1cf49e86-35de-4e60-afff-bde2def9819c spec: sourcePod: network-check-source-56499946bc-cd8l2 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T17:26:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 967.323µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:38:22Z" - latency: 2.183042ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:38:22Z" - latency: 1.14044ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:37:22Z" - latency: 2.030963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:37:22Z" - latency: 978.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:36:22Z" - latency: 1.802535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:36:22Z" - latency: 1.200126ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:35:22Z" - latency: 1.755971ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:35:22Z" - latency: 1.385473ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:34:22Z" - latency: 1.993485ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:34:22Z" kind: List metadata: resourceVersion: ""