apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "19781" uid: 7e2bf85c-4ee8-47f7-ba55-bc69a2d00f7a spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T15:32: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.185429ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 1.073464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 1.427848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:44:29Z" - latency: 1.282247ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:43:29Z" - latency: 850.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:42:29Z" - latency: 907.81µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:41:29Z" - latency: 1.472504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:40:29Z" - latency: 864.597µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:39:29Z" - latency: 914.773µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:38:29Z" - latency: 812.974µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:37:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "20915" uid: e9886362-99d4-4778-a539-0671a4f14f14 spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T15:31:29Z" message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.990431ms message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:49:29Z" - latency: 6.370417ms message: 'load-balancer-api-external: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:49:29Z" - latency: 6.050066ms message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:48:29Z" - latency: 6.404501ms message: 'load-balancer-api-external: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:48:29Z" - latency: 5.024408ms message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:47:29Z" - latency: 7.346446ms message: 'load-balancer-api-external: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:47:29Z" - latency: 4.130008ms message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 6.441706ms message: 'load-balancer-api-external: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:46:29Z" - latency: 3.926233ms message: 'load-balancer-api-external: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 6.76324ms message: 'load-balancer-api-external: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:45:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "20914" uid: 8b52077e-a818-4693-9066-6f998dc9fa97 spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T15:31:29Z" message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.583492ms message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:49:29Z" - latency: 6.447622ms message: 'load-balancer-api-internal: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:49:29Z" - latency: 5.541795ms message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:48:29Z" - latency: 6.472353ms message: 'load-balancer-api-internal: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:48:29Z" - latency: 5.041127ms message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:47:29Z" - latency: 7.451126ms message: 'load-balancer-api-internal: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:47:29Z" - latency: 4.493318ms message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 6.67553ms message: 'load-balancer-api-internal: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:46:29Z" - latency: 6.174506ms message: 'load-balancer-api-internal: tcp connection to a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 6.785169ms message: 'load-balancer-api-internal: resolved host name a0409c566b8c3474fbb17b2dcb7a1c04-f70940191eaa49d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T15:45:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-129-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "19780" uid: 846b25e7-faf0-4b7e-82ed-8866a3cb1fed spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T15:32:29Z" message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.098747ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 2.275268ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 1.968992ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:44:29Z" - latency: 2.351147ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:43:29Z" - latency: 2.383705ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:42:29Z" - latency: 2.480063ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:41:29Z" - latency: 2.13211ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:40:29Z" - latency: 2.108544ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:39:29Z" - latency: 2.42412ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:38:29Z" - latency: 2.001143ms message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:37:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-139-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "19778" uid: 514df8bd-7baf-45ed-9104-174ba3ce5be4 spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T15:32:29Z" message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.220803ms message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 1.324673ms message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 767.518µs message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:44:29Z" - latency: 1.276168ms message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:43:29Z" - latency: 1.175514ms message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:42:29Z" - latency: 1.270898ms message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:41:29Z" - latency: 765.406µs message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:40:29Z" - latency: 986.591µs message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:39:29Z" - latency: 785.095µs message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:38:29Z" - latency: 690.901µs message: 'network-check-target-ip-10-0-139-198: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:37:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-network-check-target-ip-10-0-143-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "19779" uid: 2aa09aa9-c146-404f-b326-87fbe2e292df spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T15:32:29Z" message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.353802ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 2.399522ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 2.717468ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:44:29Z" - latency: 2.142806ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:43:29Z" - latency: 2.005269ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:42:29Z" - latency: 2.091829ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:41:29Z" - latency: 2.160449ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:40:29Z" - latency: 2.053733ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:39:29Z" - latency: 2.305766ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:38:29Z" - latency: 1.778379ms message: 'network-check-target-ip-10-0-143-229: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:37:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T15:25:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-198.ec2.internal uid: 2b5fd809-a22a-434e-a1c7-14eda154ba03 resourceVersion: "20913" uid: 15652bc2-f34e-4bde-9543-cfe3c579d7f1 spec: sourcePod: network-check-source-7f44b6dd87-j9222 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T15:31:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 757.937µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:49:29Z" - latency: 1.513057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T15:49:29Z" - latency: 731.873µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:48:29Z" - latency: 1.565826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T15:48:29Z" - latency: 777.456µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:47:29Z" - latency: 1.461305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T15:47:29Z" - latency: 1.066735ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:46:29Z" - latency: 2.137951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T15:46:29Z" - latency: 888.326µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T15:45:29Z" - latency: 1.537169ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T15:45:29Z" kind: List metadata: resourceVersion: ""