apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "41939" uid: 7ca284be-6ecd-4607-9792-7477a5e37c85 spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-26T16:20:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.653µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 1.188388ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 1.360831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 809.88µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:09Z" - latency: 962.447µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:09Z" - latency: 1.078023ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:09Z" - latency: 868.768µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:09Z" - latency: 991.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:09Z" - latency: 1.431253ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:09Z" - latency: 1.080893ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "43966" uid: 26a7b1a5-f4d0-4126-940a-3b2c7de2e3d2 spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:19:09Z" message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.38977ms message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:43:09Z" - latency: 6.828791ms message: 'load-balancer-api-external: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:43:09Z" - latency: 4.320143ms message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:42:09Z" - latency: 6.74581ms message: 'load-balancer-api-external: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:42:09Z" - latency: 4.996328ms message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 10.262431ms message: 'load-balancer-api-external: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:41:09Z" - latency: 3.821675ms message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 7.283997ms message: 'load-balancer-api-external: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:09Z" - latency: 4.000125ms message: 'load-balancer-api-external: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 8.489185ms message: 'load-balancer-api-external: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "43965" uid: 83c7c067-5034-4f7b-a1c0-9358b4807d5c spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-26T16:19:09Z" message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.379303ms message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:43:09Z" - latency: 6.87334ms message: 'load-balancer-api-internal: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:43:09Z" - latency: 4.298671ms message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:42:09Z" - latency: 6.790273ms message: 'load-balancer-api-internal: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:42:09Z" - latency: 5.097095ms message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 10.328052ms message: 'load-balancer-api-internal: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:41:09Z" - latency: 5.273389ms message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 7.238992ms message: 'load-balancer-api-internal: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:09Z" - latency: 3.855156ms message: 'load-balancer-api-internal: tcp connection to af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 8.520842ms message: 'load-balancer-api-internal: resolved host name af2485520fb864473882061f71f0910b-0bb4ccad45a7de03.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-network-check-target-ip-10-0-132-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "41938" uid: 2f500d46-4151-4607-b774-7bf8f851c2c6 spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:20:09Z" message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.331138ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 2.297959ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 2.156066ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 2.296566ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:09Z" - latency: 2.121903ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:09Z" - latency: 2.286549ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:09Z" - latency: 1.925067ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:09Z" - latency: 2.59869ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:09Z" - latency: 2.763615ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:09Z" - latency: 2.233209ms message: 'network-check-target-ip-10-0-132-148: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-network-check-target-ip-10-0-133-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "41937" uid: 5da43900-165e-4b2b-9708-a932bebb5c96 spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:20:09Z" message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.103914ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 2.274583ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 2.231881ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 2.495478ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:09Z" - latency: 2.328299ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:09Z" - latency: 2.263603ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:09Z" - latency: 2.23086ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:09Z" - latency: 2.208653ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:09Z" - latency: 2.768441ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:09Z" - latency: 2.263862ms message: 'network-check-target-ip-10-0-133-107: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-network-check-target-ip-10-0-142-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "41936" uid: a7e5360c-a51b-4158-9425-577495a738ae spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-26T16:20:09Z" message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 970.872µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 1.128219ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 911.673µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 1.276503ms message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:38:09Z" - latency: 964.293µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:37:09Z" - latency: 952.276µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:36:09Z" - latency: 932.856µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:35:09Z" - latency: 834.483µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:34:09Z" - latency: 838.714µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:33:09Z" - latency: 942.614µs message: 'network-check-target-ip-10-0-142-102: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:32:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-26T16:13:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-102.ec2.internal uid: bedc4327-ad03-4b20-861a-2312d328bb39 resourceVersion: "43963" uid: 6683d095-ac0a-450f-8f31-be9c8a673007 spec: sourcePod: network-check-source-7f44b6dd87-zxjrk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-26T16:19:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 845.102µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:43:09Z" - latency: 1.605244ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:43:09Z" - latency: 1.205594ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:42:09Z" - latency: 1.84289ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:42:09Z" - latency: 732.868µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:41:09Z" - latency: 2.11538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:41:09Z" - latency: 1.025781ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:40:09Z" - latency: 1.941952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:40:09Z" - latency: 817.094µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-26T16:39:09Z" - latency: 1.64336ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-26T16:39:09Z" kind: List metadata: resourceVersion: ""