apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "29012" uid: ce2af337-4284-469f-9796-951d286c6448 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T16:32:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.407µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 1.239406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:38:31Z" - latency: 846.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:37:31Z" - latency: 1.047558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:36:31Z" - latency: 969.769µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:35:31Z" - latency: 960.408µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:34:31Z" - latency: 997.027µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:31Z" - latency: 1.143073ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:31Z" - latency: 1.191339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:31Z" - latency: 991.362µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "31549" uid: 4db782a8-2b20-48ae-998b-afe967ba5362 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:31:31Z" message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.547868ms message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:31Z" - latency: 8.131646ms message: 'load-balancer-api-external: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:43:31Z" - latency: 4.74474ms message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:42:31Z" - latency: 9.258513ms message: 'load-balancer-api-external: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:42:31Z" - latency: 4.925936ms message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:41:31Z" - latency: 7.688217ms message: 'load-balancer-api-external: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:41:31Z" - latency: 5.977909ms message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:40:31Z" - latency: 8.494786ms message: 'load-balancer-api-external: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:40:31Z" - latency: 6.249845ms message: 'load-balancer-api-external: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 8.102896ms message: 'load-balancer-api-external: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:39:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "31548" uid: cf2adb47-3478-40ff-aeb1-cdf25c4f1428 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:31:31Z" message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.358642ms message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:31Z" - latency: 8.202658ms message: 'load-balancer-api-internal: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:43:31Z" - latency: 4.751797ms message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:42:31Z" - latency: 9.388731ms message: 'load-balancer-api-internal: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:42:31Z" - latency: 4.919702ms message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:41:31Z" - latency: 7.764603ms message: 'load-balancer-api-internal: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:41:31Z" - latency: 5.049128ms message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:40:31Z" - latency: 8.359586ms message: 'load-balancer-api-internal: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:40:31Z" - latency: 6.001577ms message: 'load-balancer-api-internal: tcp connection to a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 8.192675ms message: 'load-balancer-api-internal: resolved host name a2e687080fe414a6896897c9d38bd61f-ccc2fc93a144371e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T16:39:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-128-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "29009" uid: 3c3c84ae-24ea-4c10-8653-cdb8ac476b11 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:32:31Z" message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.181µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 873.07µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:38:31Z" - latency: 817.639µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:37:31Z" - latency: 890.108µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:36:31Z" - latency: 990.304µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:35:31Z" - latency: 897.736µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:34:31Z" - latency: 1.224774ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:31Z" - latency: 1.43333ms message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:31Z" - latency: 854.707µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:31Z" - latency: 876.548µs message: 'network-check-target-ip-10-0-128-17: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-130-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "29010" uid: 7b03e7b3-bef2-48a7-9ccc-3c74a986cf37 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:32:31Z" message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.106426ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 2.236489ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:38:31Z" - latency: 2.281803ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:37:31Z" - latency: 2.660537ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:36:31Z" - latency: 2.218127ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:35:31Z" - latency: 2.048236ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:34:31Z" - latency: 2.458022ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:31Z" - latency: 2.485249ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:31Z" - latency: 2.469099ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:31Z" - latency: 1.883246ms message: 'network-check-target-ip-10-0-130-239: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-network-check-target-ip-10-0-140-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "29011" uid: 721f618a-daa8-4342-a407-170c3132a3d9 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:32:31Z" message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.612564ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 2.092335ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:38:31Z" - latency: 2.595994ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:37:31Z" - latency: 1.901178ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:36:31Z" - latency: 2.089519ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:35:31Z" - latency: 2.364196ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:34:31Z" - latency: 1.949431ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:33:31Z" - latency: 2.600173ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:32:31Z" - latency: 2.513873ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:31:31Z" - latency: 2.16809ms message: 'network-check-target-ip-10-0-140-63: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:25:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-17.ec2.internal uid: 12fbab3f-52aa-4851-8a13-d206347d9f7c resourceVersion: "31546" uid: 043c7fc4-757f-44ab-9110-01a4affb6c43 spec: sourcePod: network-check-source-dbd9cf844-ggjfx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T16:31:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.541µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:43:31Z" - latency: 1.623017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:43:31Z" - latency: 869.459µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:42:31Z" - latency: 1.63528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:42:31Z" - latency: 1.102624ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:41:31Z" - latency: 1.649667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:41:31Z" - latency: 1.169371ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:40:31Z" - latency: 2.100324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:40:31Z" - latency: 954.558µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:39:31Z" - latency: 1.964973ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T16:39:31Z" kind: List metadata: resourceVersion: ""