apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "45374" uid: e4d377d0-e058-4bf2-8282-a8ddf310d015 spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T18:01:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.404959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 1.726363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 1.05944ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 942.073µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:19:59Z" - latency: 993.343µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:18:59Z" - latency: 1.120966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:17:59Z" - latency: 1.260133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:16:59Z" - latency: 949.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:15:59Z" - latency: 1.351025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:14:59Z" - latency: 994.307µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "47421" uid: 6392fa54-a32b-4896-9f17-c244f8eccb2b spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:00:59Z" message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.834615ms message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:24:59Z" - latency: 8.771964ms message: 'load-balancer-api-external: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:24:59Z" - latency: 5.778044ms message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:23:59Z" - latency: 7.764591ms message: 'load-balancer-api-external: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:23:59Z" - latency: 4.939001ms message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 7.03598ms message: 'load-balancer-api-external: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:22:59Z" - latency: 5.089319ms message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 10.237445ms message: 'load-balancer-api-external: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:21:59Z" - latency: 5.589843ms message: 'load-balancer-api-external: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 8.190098ms message: 'load-balancer-api-external: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:20:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "47420" uid: f2cbc4a0-42f0-4c66-97d0-fa57a33aa7ff spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:00:59Z" message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.847204ms message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:24:59Z" - latency: 8.710967ms message: 'load-balancer-api-internal: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:24:59Z" - latency: 4.662558ms message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:23:59Z" - latency: 7.745922ms message: 'load-balancer-api-internal: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:23:59Z" - latency: 4.582394ms message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 6.972644ms message: 'load-balancer-api-internal: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:22:59Z" - latency: 6.093734ms message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 10.262046ms message: 'load-balancer-api-internal: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:21:59Z" - latency: 5.62457ms message: 'load-balancer-api-internal: tcp connection to aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 8.221529ms message: 'load-balancer-api-internal: resolved host name aee30b74643cb40ae8589cb6ed892333-ff940504ee28eaa1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:20:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-128-168 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "45373" uid: 02da2fd1-82ba-4a54-b19f-6839e4d25974 spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:01:59Z" message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.403066ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 2.291941ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 2.456005ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 2.799745ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:19:59Z" - latency: 2.604647ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:18:59Z" - latency: 1.985306ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:17:59Z" - latency: 2.270402ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:16:59Z" - latency: 2.426149ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:15:59Z" - latency: 2.305043ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:14:59Z" - latency: 2.45365ms message: 'network-check-target-ip-10-0-128-168: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-139-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "45371" uid: c50b27f7-65b6-4cb3-b074-19a25d3c8496 spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:01:59Z" message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.20212ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 1.921764ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 1.410908ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 1.686877ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:19:59Z" - latency: 1.299381ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:18:59Z" - latency: 866.837µs message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:17:59Z" - latency: 1.576585ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:16:59Z" - latency: 931.349µs message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:15:59Z" - latency: 1.219318ms message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:14:59Z" - latency: 897.859µs message: 'network-check-target-ip-10-0-139-141: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-network-check-target-ip-10-0-143-199 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "45372" uid: c44de1ae-0a4f-496e-921f-5418357d7456 spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:01:59Z" message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.210856ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 2.932849ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 2.507026ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 2.338362ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:19:59Z" - latency: 2.455763ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:18:59Z" - latency: 2.047847ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:17:59Z" - latency: 2.729697ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:16:59Z" - latency: 2.574707ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:15:59Z" - latency: 2.71343ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:14:59Z" - latency: 2.188883ms message: 'network-check-target-ip-10-0-143-199: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:13:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T17:54:57Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-141-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-141.ec2.internal uid: ad4c32dd-d121-494a-91ae-d73306ec8739 resourceVersion: "47418" uid: c9026770-2904-4150-8a6b-0ad4b6cff9a9 spec: sourcePod: network-check-source-dbd9cf844-szrts targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T18:00:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.044µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:24:59Z" - latency: 1.748889ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:24:59Z" - latency: 926.572µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:23:59Z" - latency: 1.890846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:23:59Z" - latency: 1.045675ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:22:59Z" - latency: 2.226405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:22:59Z" - latency: 927.164µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:21:59Z" - latency: 2.290279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:21:59Z" - latency: 971.518µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:20:59Z" - latency: 1.804005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:20:59Z" kind: List metadata: resourceVersion: ""