apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "43629" uid: 81fb2654-d51c-46ae-a74b-b9ef2bea2b08 spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T14:20:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.029203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 967.786µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 1.394801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 1.138333ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 1.111614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:05Z" - latency: 1.423523ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:05Z" - latency: 1.186287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:05Z" - latency: 1.078146ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:05Z" - latency: 1.211764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:05Z" - latency: 1.154262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "44524" uid: ff7d7b44-2bfc-48b7-aded-e780a73abf4a spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:19:05Z" message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.803107ms message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:05Z" - latency: 7.594746ms message: 'load-balancer-api-external: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:49:05Z" - latency: 5.343854ms message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 7.950318ms message: 'load-balancer-api-external: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:48:05Z" - latency: 4.851713ms message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 8.046149ms message: 'load-balancer-api-external: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:47:05Z" - latency: 6.422279ms message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 15.120675ms message: 'load-balancer-api-external: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:46:05Z" - latency: 4.645597ms message: 'load-balancer-api-external: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 7.870079ms message: 'load-balancer-api-external: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "44525" uid: f62d4be4-fd45-498b-bfef-328ec19e830b spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:19:05Z" message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.831605ms message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:05Z" - latency: 7.541726ms message: 'load-balancer-api-internal: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:49:05Z" - latency: 3.891921ms message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 7.908813ms message: 'load-balancer-api-internal: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:48:05Z" - latency: 5.607399ms message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 8.081485ms message: 'load-balancer-api-internal: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:47:05Z" - latency: 3.25061ms message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 15.098644ms message: 'load-balancer-api-internal: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:46:05Z" - latency: 4.849434ms message: 'load-balancer-api-internal: tcp connection to a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 7.803282ms message: 'load-balancer-api-internal: resolved host name a57988d183e814678a784aaad31669b4-20fe5164e3b8b9e8.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-network-check-target-ip-10-0-135-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "43626" uid: a0f3601f-7fc6-431a-91ee-c4bab57a99d5 spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:20:05Z" message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 760.231µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 929.811µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 701.562µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 786.352µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 960.419µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:05Z" - latency: 840.868µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:05Z" - latency: 807.995µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:05Z" - latency: 836.538µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:05Z" - latency: 1.145173ms message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:05Z" - latency: 777.172µs message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-network-check-target-ip-10-0-139-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "43627" uid: a427bf40-f570-4543-a278-5cc48423c849 spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:20:05Z" message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.238756ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 2.564382ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 2.321623ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 2.348598ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 2.209064ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:05Z" - latency: 2.111555ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:05Z" - latency: 2.218802ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:05Z" - latency: 2.236364ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:05Z" - latency: 2.306261ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:05Z" - latency: 1.964697ms message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-network-check-target-ip-10-0-142-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "43628" uid: e8841760-8956-4ff7-aa70-15443e3714bf spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:20:05Z" message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.765234ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 1.731904ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 1.85162ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 1.846818ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 1.759352ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:44:05Z" - latency: 1.804781ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:43:05Z" - latency: 1.86326ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:42:05Z" - latency: 1.966017ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:41:05Z" - latency: 1.667962ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:40:05Z" - latency: 1.786236ms message: 'network-check-target-ip-10-0-142-164: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:39:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T14:13:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-120-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-120.ec2.internal uid: 3213517b-0fa5-47f1-af81-f8ee154d092e resourceVersion: "44523" uid: 8da83462-20f2-4fb6-9f11-9445c17c4e80 spec: sourcePod: network-check-source-7f44b6dd87-zj6rj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T14:19:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.127777ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:49:05Z" - latency: 1.641029ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:49:05Z" - latency: 955.578µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:48:05Z" - latency: 1.639904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:48:05Z" - latency: 1.150584ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:47:05Z" - latency: 1.702266ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:47:05Z" - latency: 858.414µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:46:05Z" - latency: 1.770174ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:46:05Z" - latency: 1.21067ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:45:05Z" - latency: 1.686657ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:45:05Z" kind: List metadata: resourceVersion: ""