apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "21818" uid: 59e7d696-e94e-4f71-890b-6d7bca8db119 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T14:25:31Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.224453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:31Z" - latency: 1.537152ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:31Z" - latency: 1.026496ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:31Z" - latency: 1.037383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 963.02µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 1.587796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 1.019275ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 1.121175ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 969.812µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:31Z" - latency: 1.091109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "20207" uid: 91cb7987-ddde-4ee5-985b-a61292c4215a spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:24:31Z" message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.545326ms message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 9.995652ms message: 'load-balancer-api-external: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:31Z" - latency: 5.743914ms message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 10.224446ms message: 'load-balancer-api-external: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:31Z" - latency: 4.21613ms message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 9.000672ms message: 'load-balancer-api-external: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:31Z" - latency: 4.562937ms message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 9.02899ms message: 'load-balancer-api-external: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:31Z" - latency: 5.022737ms message: 'load-balancer-api-external: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 10.947284ms message: 'load-balancer-api-external: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "20206" uid: f358207c-3e24-4f7d-98f6-fb37adc1ed75 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T14:24:31Z" message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.559739ms message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 9.934653ms message: 'load-balancer-api-internal: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:31Z" - latency: 5.715601ms message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 10.176159ms message: 'load-balancer-api-internal: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:31Z" - latency: 4.241686ms message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 8.902126ms message: 'load-balancer-api-internal: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:31Z" - latency: 4.600338ms message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 8.991218ms message: 'load-balancer-api-internal: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:31Z" - latency: 4.967923ms message: 'load-balancer-api-internal: tcp connection to a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 10.899881ms message: 'load-balancer-api-internal: resolved host name a345b7d03735c4d45846412f93a24ae0-d739e54db5cdc475.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-132-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "21816" uid: 25392e9e-3f5e-47f0-980c-ffd7b3701b65 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:31Z" message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.762059ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:31Z" - latency: 2.403446ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:31Z" - latency: 2.514723ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:31Z" - latency: 2.624886ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 2.190827ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 2.418848ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 2.137085ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 2.60822ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 2.170656ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:31Z" - latency: 2.248737ms message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-136-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "21815" uid: 1e6eb633-ae69-41b8-a37d-e24fd4de5694 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:31Z" message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.626µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:31Z" - latency: 944.333µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:31Z" - latency: 891.205µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:31Z" - latency: 1.585976ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 1.120892ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 939.048µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 1.380057ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 1.731416ms message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 937.396µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:31Z" - latency: 801.824µs message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-138-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "21817" uid: a19ee936-4c97-4349-b9ad-f9ec0658d943 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T14:25:31Z" message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.314799ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:39:31Z" - latency: 2.320282ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:38:31Z" - latency: 2.416251ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:37:31Z" - latency: 2.507502ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 2.335883ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 2.342906ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 2.298077ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 2.746498ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 2.036162ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:31:31Z" - latency: 2.128119ms message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:30:31Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T14:18:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-70-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-70.ec2.internal uid: 3dd19e53-2a4b-413e-bd8e-2d9f5c9806bb resourceVersion: "20205" uid: f9a64be9-b894-4ca7-8566-901e2eed1b49 spec: sourcePod: network-check-source-56499946bc-k4k92 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T14:24:31Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 905.064µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:36:31Z" - latency: 2.049566ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:36:31Z" - latency: 1.018015ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:35:31Z" - latency: 2.099185ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:35:31Z" - latency: 720.695µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:34:31Z" - latency: 1.889868ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:34:31Z" - latency: 1.381803ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:33:31Z" - latency: 1.86758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:33:31Z" - latency: 976.992µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T14:32:31Z" - latency: 2.15724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T14:32:31Z" kind: List metadata: resourceVersion: ""