apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "45177" uid: 67fd978c-f003-4051-b097-bdde3b0fcb50 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T20:07:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.083µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 918.55µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 930.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 1.076767ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:25:47Z" - latency: 844.871µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:24:47Z" - latency: 1.221083ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:23:47Z" - latency: 1.006074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:22:47Z" - latency: 825.923µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:21:47Z" - latency: 972.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:20:47Z" - latency: 1.206437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "47538" uid: 18656919-572e-4d73-834e-886324e53709 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T20:06:47Z" message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.921936ms message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:47Z" - latency: 6.58173ms message: 'load-balancer-api-external: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:30:47Z" - latency: 4.920084ms message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:47Z" - latency: 6.895221ms message: 'load-balancer-api-external: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:29:47Z" - latency: 4.801535ms message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 6.758991ms message: 'load-balancer-api-external: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:28:47Z" - latency: 4.124ms message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 12.598992ms message: 'load-balancer-api-external: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:27:47Z" - latency: 3.826551ms message: 'load-balancer-api-external: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 11.131709ms message: 'load-balancer-api-external: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:26:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "47539" uid: 3dc1a775-2f54-4300-bd73-378055b88081 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T20:06:47Z" message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.921875ms message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:47Z" - latency: 6.490856ms message: 'load-balancer-api-internal: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:30:47Z" - latency: 5.057347ms message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:47Z" - latency: 6.77712ms message: 'load-balancer-api-internal: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:29:47Z" - latency: 4.468629ms message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 6.691579ms message: 'load-balancer-api-internal: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:28:47Z" - latency: 4.132378ms message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 12.520746ms message: 'load-balancer-api-internal: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:27:47Z" - latency: 5.782185ms message: 'load-balancer-api-internal: tcp connection to a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 11.003637ms message: 'load-balancer-api-internal: resolved host name a59d810388c6e498a8f0a4396bbf44db-cc5ed20e6be7717e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T20:26:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-129-157 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "45174" uid: 6773c08f-c574-44b4-bf51-d6fbd991ef3e spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:07:47Z" message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.437944ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 819.838µs message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 947µs message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 1.262502ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:25:47Z" - latency: 867.857µs message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:24:47Z" - latency: 830.471µs message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:23:47Z" - latency: 1.38666ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:22:47Z" - latency: 1.069895ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:21:47Z" - latency: 1.210675ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:20:47Z" - latency: 1.086145ms message: 'network-check-target-ip-10-0-129-157: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-130-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "45175" uid: f241d738-8c69-4873-be52-454d8452d398 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:07:47Z" message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.520866ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 2.849389ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 2.967114ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 2.612665ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:25:47Z" - latency: 2.307746ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:24:47Z" - latency: 2.101776ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:23:47Z" - latency: 2.749252ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:22:47Z" - latency: 2.229631ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:21:47Z" - latency: 2.476822ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:20:47Z" - latency: 3.025289ms message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-network-check-target-ip-10-0-132-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "45176" uid: 59ac6b39-4c26-47d1-b6d6-beb0e5aed288 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T20:07:47Z" message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.308422ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 2.211525ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 2.157567ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 2.02704ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:25:47Z" - latency: 1.856456ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:24:47Z" - latency: 1.725438ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:23:47Z" - latency: 2.129839ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:22:47Z" - latency: 2.567305ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:21:47Z" - latency: 2.166054ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:20:47Z" - latency: 2.344115ms message: 'network-check-target-ip-10-0-132-215: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:19:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T20:00:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-157-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-157.ec2.internal uid: 40fcd0c9-a40b-4738-85aa-716049e6e9bf resourceVersion: "47537" uid: 63647c4c-7837-46c3-a41e-f0d15ab1c381 spec: sourcePod: network-check-source-56d84b9f44-2lf95 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T20:06:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.873µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:30:47Z" - latency: 1.649818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:30:47Z" - latency: 862.484µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:29:47Z" - latency: 1.821209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:29:47Z" - latency: 811.774µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:28:47Z" - latency: 1.724905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:28:47Z" - latency: 1.216607ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:27:47Z" - latency: 1.735025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:27:47Z" - latency: 1.67133ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T20:26:47Z" - latency: 1.727332ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T20:26:47Z" kind: List metadata: resourceVersion: ""