apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52161" uid: a6dec495-f5c9-4add-a19e-7c97f3198e4a spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T16:31:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.299µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 945.178µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 1.104173ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 1.081989ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 1.119616ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 1.371219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:01:40Z" - latency: 1.202956ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:00:40Z" - latency: 1.538947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:59:40Z" - latency: 899.863µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:58:40Z" - latency: 869.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52163" uid: 6d6a3da4-0a3b-4a98-ace9-63ecdedcde6f spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:30:40Z" message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.526334ms message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 10.639054ms message: 'load-balancer-api-external: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:40Z" - latency: 4.785006ms message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 7.130674ms message: 'load-balancer-api-external: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:40Z" - latency: 5.364739ms message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 6.522753ms message: 'load-balancer-api-external: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:40Z" - latency: 4.938461ms message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 6.27767ms message: 'load-balancer-api-external: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:03:40Z" - latency: 3.211605ms message: 'load-balancer-api-external: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 10.210089ms message: 'load-balancer-api-external: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:02:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52162" uid: 91c603cf-6e57-4f4a-8f38-6b061a248799 spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T16:30:40Z" message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.46684ms message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 10.69948ms message: 'load-balancer-api-internal: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:40Z" - latency: 7.096131ms message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 7.192693ms message: 'load-balancer-api-internal: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:40Z" - latency: 5.232416ms message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 6.595198ms message: 'load-balancer-api-internal: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:40Z" - latency: 4.278617ms message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 6.292443ms message: 'load-balancer-api-internal: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:03:40Z" - latency: 3.185146ms message: 'load-balancer-api-internal: tcp connection to a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 10.229997ms message: 'load-balancer-api-internal: resolved host name a5e111ce45e794fdda34551edee267cc-6b8402d51215da6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T17:02:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-network-check-target-ip-10-0-128-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52159" uid: 5fcf5b30-262e-42ca-a750-e2b3f68b5288 spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:31:40Z" message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.296873ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 2.338681ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 2.568064ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 2.19696ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 2.226786ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 2.77994ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:01:40Z" - latency: 2.683933ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:00:40Z" - latency: 2.467781ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:59:40Z" - latency: 2.566944ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:58:40Z" - latency: 1.887122ms message: 'network-check-target-ip-10-0-128-162: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-network-check-target-ip-10-0-129-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52158" uid: 587be476-0927-4b9f-b46c-ea0f18d6b9a4 spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:31:40Z" message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.061563ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 2.051963ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 2.088176ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 2.216074ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 2.29231ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 2.270057ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:01:40Z" - latency: 2.293093ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:00:40Z" - latency: 2.018234ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:59:40Z" - latency: 2.16633ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:58:40Z" - latency: 2.137369ms message: 'network-check-target-ip-10-0-129-97: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-network-check-target-ip-10-0-134-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52157" uid: ba859734-a792-459f-89ae-37967f17c30a spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T16:31:40Z" message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 865.846µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 894.586µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 948.847µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 923.182µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 849.323µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 917.523µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:01:40Z" - latency: 1.296396ms message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:00:40Z" - latency: 738.424µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:59:40Z" - latency: 1.109873ms message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:58:40Z" - latency: 891.336µs message: 'network-check-target-ip-10-0-134-86: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T16:57:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T16:24:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-86-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-86.ec2.internal uid: f6aa7832-e09a-419c-882a-ceb375b0518a resourceVersion: "52160" uid: ecef5ddc-39e9-453f-9d00-6144bbee48b2 spec: sourcePod: network-check-source-dbd9cf844-69ffk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T16:30:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.35625ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:06:40Z" - latency: 1.808998ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:06:40Z" - latency: 939.53µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:05:40Z" - latency: 2.09378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:05:40Z" - latency: 845.807µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:04:40Z" - latency: 1.826321ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:04:40Z" - latency: 819.832µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:03:40Z" - latency: 1.679649ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:03:40Z" - latency: 847.228µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T17:02:40Z" - latency: 1.838487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T17:02:40Z" kind: List metadata: resourceVersion: ""