apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "44689" uid: 68342db7-3107-4dae-b704-030ce78442b7 spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T18:38:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 951.76µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 1.11485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 1.09803ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 1.20734ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:56:29Z" - latency: 1.106628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:55:29Z" - latency: 901.19µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:54:29Z" - latency: 927.742µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:53:29Z" - latency: 1.029872ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:52:29Z" - latency: 801.578µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:51:29Z" - latency: 1.075698ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "46952" uid: 62e58fe7-adcd-4bc2-9090-85f679540a90 spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T18:37:29Z" message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.874857ms message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:01:29Z" - latency: 9.554934ms message: 'load-balancer-api-external: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:01:29Z" - latency: 4.425977ms message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:00:29Z" - latency: 9.015372ms message: 'load-balancer-api-external: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:00:29Z" - latency: 5.238549ms message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 7.350438ms message: 'load-balancer-api-external: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:59:29Z" - latency: 4.629861ms message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 6.729503ms message: 'load-balancer-api-external: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:58:29Z" - latency: 3.83759ms message: 'load-balancer-api-external: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 9.225914ms message: 'load-balancer-api-external: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "46953" uid: 2bd9b1c2-70ce-403b-94f3-444bbf4bc6bd spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T18:37:29Z" message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.329119ms message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:01:29Z" - latency: 9.633207ms message: 'load-balancer-api-internal: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:01:29Z" - latency: 3.707972ms message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:00:29Z" - latency: 9.133723ms message: 'load-balancer-api-internal: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:00:29Z" - latency: 5.228422ms message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 7.420802ms message: 'load-balancer-api-internal: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:59:29Z" - latency: 4.671492ms message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 6.672162ms message: 'load-balancer-api-internal: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:58:29Z" - latency: 3.708882ms message: 'load-balancer-api-internal: tcp connection to a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 9.301694ms message: 'load-balancer-api-internal: resolved host name a6c160db9343a42ca977ba3bed0128ca-e2bf7e3e929cbbab.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:57:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-network-check-target-ip-10-0-133-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "44686" uid: 99a879bb-55d6-4517-bd96-1671180e8b44 spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:38:29Z" message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.891662ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 1.992419ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 2.013321ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 2.182038ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:56:29Z" - latency: 2.106999ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:55:29Z" - latency: 1.908714ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:54:29Z" - latency: 2.182117ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:53:29Z" - latency: 2.038631ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:52:29Z" - latency: 2.000081ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:51:29Z" - latency: 2.179539ms message: 'network-check-target-ip-10-0-133-168: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-network-check-target-ip-10-0-137-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "44688" uid: 47ecf597-19e7-4e01-9ea6-79313b2f5c22 spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:38:29Z" message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.465344ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 2.073208ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 2.446006ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 2.459466ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:56:29Z" - latency: 2.04137ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:55:29Z" - latency: 2.05895ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:54:29Z" - latency: 2.092435ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:53:29Z" - latency: 2.4824ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:52:29Z" - latency: 2.248198ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:51:29Z" - latency: 2.206719ms message: 'network-check-target-ip-10-0-137-19: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-network-check-target-ip-10-0-140-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "44687" uid: b2f70db0-837c-4155-8abe-5e539ae4543b spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:38:29Z" message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.583µs message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 1.231811ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 884.274µs message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 1.486747ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:56:29Z" - latency: 926.021µs message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:55:29Z" - latency: 855.243µs message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:54:29Z" - latency: 1.237799ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:53:29Z" - latency: 1.258189ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:52:29Z" - latency: 1.851407ms message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:51:29Z" - latency: 888.684µs message: 'network-check-target-ip-10-0-140-205: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:50:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:31:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-205.ec2.internal uid: d5ea6d05-bbc9-435a-8b7e-3a980155d318 resourceVersion: "46950" uid: f7b03e94-fe50-4ada-bc5a-edd0b11af00b spec: sourcePod: network-check-source-7f44b6dd87-8gns8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T18:37:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 897.897µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:01:29Z" - latency: 1.774161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:01:29Z" - latency: 1.141551ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:00:29Z" - latency: 1.848792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:00:29Z" - latency: 782.05µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:59:29Z" - latency: 1.90487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:59:29Z" - latency: 955.762µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:58:29Z" - latency: 2.164723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:58:29Z" - latency: 882.239µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:57:29Z" - latency: 1.837612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:57:29Z" kind: List metadata: resourceVersion: ""