apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "45672" uid: 23098a00-eaa2-49a4-91ce-316038dcf384 spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T23:55:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.217965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 1.517399ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 1.199973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 1.048565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:13:57Z" - latency: 1.231014ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:12:57Z" - latency: 835.04µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:11:57Z" - latency: 982.993µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:10:57Z" - latency: 858.921µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:09:57Z" - latency: 974.514µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:08:57Z" - latency: 963.181µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "47826" uid: 2db3e701-d719-4d33-b13c-d81d73eddf20 spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T23:54:57Z" message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.442069ms message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:18:57Z" - latency: 7.01761ms message: 'load-balancer-api-external: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:18:57Z" - latency: 5.050868ms message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:17:57Z" - latency: 7.914186ms message: 'load-balancer-api-external: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:17:57Z" - latency: 4.159356ms message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 9.647098ms message: 'load-balancer-api-external: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:16:57Z" - latency: 2.713471ms message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 6.565043ms message: 'load-balancer-api-external: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:15:57Z" - latency: 4.453122ms message: 'load-balancer-api-external: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 8.618585ms message: 'load-balancer-api-external: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "47825" uid: a0047274-442c-4dba-ad0f-aeb1ea1001cd spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T23:54:57Z" message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.94891ms message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:18:57Z" - latency: 7.067127ms message: 'load-balancer-api-internal: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:18:57Z" - latency: 5.026435ms message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:17:57Z" - latency: 8.017975ms message: 'load-balancer-api-internal: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:17:57Z" - latency: 4.113711ms message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 9.688561ms message: 'load-balancer-api-internal: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:16:57Z" - latency: 4.148552ms message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 6.585677ms message: 'load-balancer-api-internal: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:15:57Z" - latency: 4.450514ms message: 'load-balancer-api-internal: tcp connection to a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 8.756691ms message: 'load-balancer-api-internal: resolved host name a9e8f24794a8c459cac9494dd3610bc6-7f26e191f9c16c9c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-10T00:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-network-check-target-ip-10-0-129-49 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "45669" uid: 88855dd1-04ed-4878-8f0b-fa4f7b78612c spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-09T23:55:57Z" message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.792µs message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 1.221994ms message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 843.075µs message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 1.222911ms message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:13:57Z" - latency: 1.437645ms message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:12:57Z" - latency: 967.985µs message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:11:57Z" - latency: 746.102µs message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:10:57Z" - latency: 950.258µs message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:09:57Z" - latency: 1.586206ms message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:08:57Z" - latency: 1.00866ms message: 'network-check-target-ip-10-0-129-49: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-network-check-target-ip-10-0-131-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "45671" uid: 191321a9-4fa0-4539-8705-a3ae5a6c0f75 spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T23:55:57Z" message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.332424ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 2.155915ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 2.36293ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 2.226552ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:13:57Z" - latency: 2.22531ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:12:57Z" - latency: 2.111462ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:11:57Z" - latency: 2.139643ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:10:57Z" - latency: 2.108703ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:09:57Z" - latency: 2.396509ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:08:57Z" - latency: 1.952494ms message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-network-check-target-ip-10-0-132-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "45670" uid: 37d9d614-9dae-44c2-aea8-baf96cecfdca spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T23:55:57Z" message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.160846ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 2.117341ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 1.920634ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 2.351062ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:13:57Z" - latency: 2.091396ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:12:57Z" - latency: 2.085604ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:11:57Z" - latency: 2.164591ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:10:57Z" - latency: 2.070705ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:09:57Z" - latency: 1.746789ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:08:57Z" - latency: 1.987346ms message: 'network-check-target-ip-10-0-132-56: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:07:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T23:48:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-49-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-49.ec2.internal uid: 10b52a23-9ce6-4fb7-a918-d17ff0cd1c87 resourceVersion: "47824" uid: f87b3687-7cf5-42d6-a8e0-2f4afa8a8910 spec: sourcePod: network-check-source-dbd9cf844-5k98g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T23:54:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.889µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:18:57Z" - latency: 1.911845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T00:18:57Z" - latency: 920.992µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:17:57Z" - latency: 1.637308ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T00:17:57Z" - latency: 891.989µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:16:57Z" - latency: 1.636746ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T00:16:57Z" - latency: 865.252µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:15:57Z" - latency: 1.739302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T00:15:57Z" - latency: 802.166µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-10T00:14:57Z" - latency: 1.69736ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-10T00:14:57Z" kind: List metadata: resourceVersion: ""