apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "38030" uid: 8a759694-831a-439f-af64-4f4959319279 spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-15T16:48:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 945.455µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:30Z" - latency: 805.834µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:30Z" - latency: 1.368051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:30Z" - latency: 1.108557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 1.259919ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 1.066502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 1.213514ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 979.129µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 1.137556ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:30Z" - latency: 1.212217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "35634" uid: 14ff1c57-2faa-42e8-8e8d-8c50a2220468 spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:47:30Z" message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.279678ms message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 10.630048ms message: 'load-balancer-api-external: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:30Z" - latency: 3.424907ms message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 8.616096ms message: 'load-balancer-api-external: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:30Z" - latency: 5.622025ms message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 6.956992ms message: 'load-balancer-api-external: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:57:30Z" - latency: 4.357896ms message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 8.782305ms message: 'load-balancer-api-external: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:56:30Z" - latency: 4.832186ms message: 'load-balancer-api-external: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 8.992495ms message: 'load-balancer-api-external: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:55:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "35633" uid: 498c6f78-4a14-4aa9-bb8a-2f227ce69d8a spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-15T16:47:30Z" message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.17537ms message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 10.553845ms message: 'load-balancer-api-internal: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:30Z" - latency: 3.393441ms message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 8.581493ms message: 'load-balancer-api-internal: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:30Z" - latency: 3.237958ms message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 6.90908ms message: 'load-balancer-api-internal: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:57:30Z" - latency: 5.593292ms message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 8.717171ms message: 'load-balancer-api-internal: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:56:30Z" - latency: 6.941654ms message: 'load-balancer-api-internal: tcp connection to a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 8.81587ms message: 'load-balancer-api-internal: resolved host name a634c20fb41b3456486b828bd417c714-c5bc69e3f07b170f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-15T16:55:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-133-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "38027" uid: 766cd5cc-e113-4ffd-9a74-f34a89fa0fc4 spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:48:30Z" message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 802.164µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:30Z" - latency: 950.331µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:30Z" - latency: 846.317µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:30Z" - latency: 852.452µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 1.375077ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 909.577µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 1.104757ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 1.30589ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 1.306802ms message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:30Z" - latency: 928.992µs message: 'network-check-target-ip-10-0-133-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-138-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "38029" uid: eaf44aea-838f-422c-98df-14ebc6268cb4 spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:48:30Z" message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.246934ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:30Z" - latency: 2.429188ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:30Z" - latency: 2.004032ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:30Z" - latency: 1.882261ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 1.803557ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 2.214292ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 1.957712ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 2.569587ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 1.991422ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:30Z" - latency: 2.432757ms message: 'network-check-target-ip-10-0-138-140: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-ip-10-0-142-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "38028" uid: 4dc14e2f-3f85-4612-8c10-9e0c11b233ae spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-15T16:48:30Z" message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.07806ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:02:30Z" - latency: 1.882814ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:01:30Z" - latency: 2.122116ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T17:00:30Z" - latency: 2.01396ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 2.206538ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 2.016867ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 2.262306ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 2.298805ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 1.805099ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:54:30Z" - latency: 1.966674ms message: 'network-check-target-ip-10-0-142-145: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:53:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-15T16:41:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-214.ec2.internal uid: 16a23833-da05-4017-9856-aef39aad754a resourceVersion: "35632" uid: cbd24f5d-1974-41f0-854f-6ac6ffe3356c spec: sourcePod: network-check-source-869dcfcdcd-9hfrv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-15T16:47:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 895.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:59:30Z" - latency: 1.627056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:59:30Z" - latency: 1.008401ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:58:30Z" - latency: 1.7455ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:58:30Z" - latency: 1.013311ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:57:30Z" - latency: 1.896079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:57:30Z" - latency: 823.802µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:56:30Z" - latency: 1.753049ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:56:30Z" - latency: 1.001195ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-15T16:55:30Z" - latency: 1.783057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-15T16:55:30Z" kind: List metadata: resourceVersion: ""