apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31929" uid: 5ae891b2-2b67-46ed-a67e-19280a86c5f5 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T18:29:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 1.189837ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 1.038031ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 863.363µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 916.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 969.476µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:21Z" - latency: 1.248535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:21Z" - latency: 1.318158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:21Z" - latency: 917.861µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:21Z" - latency: 853.292µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31930" uid: 2eddb3c8-466e-4b10-9afc-9066791a84db spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:28:21Z" message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.425837ms message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 6.683136ms message: 'load-balancer-api-external: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:04:21Z" - latency: 5.769159ms message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 6.955256ms message: 'load-balancer-api-external: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:03:21Z" - latency: 3.964175ms message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 6.540125ms message: 'load-balancer-api-external: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:02:21Z" - latency: 3.462297ms message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 7.743795ms message: 'load-balancer-api-external: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:21Z" - latency: 4.841095ms message: 'load-balancer-api-external: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 6.839407ms message: 'load-balancer-api-external: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31931" uid: f81ffd2a-3b5c-48a2-873b-a6414f2b64c4 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T18:28:21Z" message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.427472ms message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 6.701912ms message: 'load-balancer-api-internal: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:04:21Z" - latency: 5.754781ms message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 6.890389ms message: 'load-balancer-api-internal: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:03:21Z" - latency: 3.996244ms message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 6.468515ms message: 'load-balancer-api-internal: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:02:21Z" - latency: 4.339953ms message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 7.838742ms message: 'load-balancer-api-internal: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:21Z" - latency: 4.009187ms message: 'load-balancer-api-internal: tcp connection to a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 6.773413ms message: 'load-balancer-api-internal: resolved host name a0ef19ffc5cc54786a666097119e3e3e-3b7ac0c9cf67968a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-128-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31927" uid: 2fc14cc9-2188-4ca8-874a-321d858b0948 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:21Z" message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267261ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 2.30169ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 2.630276ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 2.606794ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 2.137513ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 2.453958ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:21Z" - latency: 2.2776ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:21Z" - latency: 2.761629ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:21Z" - latency: 2.33718ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:21Z" - latency: 2.235123ms message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-134-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31928" uid: 48ff2bcb-88a9-4029-9f51-af3ac85b1f04 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:21Z" message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.077433ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 2.450318ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 2.345974ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 2.150009ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 2.153983ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 2.055018ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:21Z" - latency: 1.951951ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:21Z" - latency: 2.305539ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:21Z" - latency: 2.218888ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:21Z" - latency: 2.084171ms message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-network-check-target-ip-10-0-138-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31925" uid: 648509ec-ccba-425a-9c5c-19458ef6bc21 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T18:29:21Z" message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 927.253µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 1.077619ms message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 1.221565ms message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 945.979µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 868.713µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 876.943µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:59:21Z" - latency: 969.969µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:58:21Z" - latency: 1.442175ms message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:57:21Z" - latency: 862.595µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:56:21Z" - latency: 998.658µs message: 'network-check-target-ip-10-0-138-88: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T18:55:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T18:22:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-88.ec2.internal uid: d149bbc8-4101-4c36-b5c0-c8fa3ed13983 resourceVersion: "31926" uid: 7c6e2078-df4e-4eda-bb13-4ee2bb36d7d1 spec: sourcePod: network-check-source-7b678d77c7-rlbq9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T18:28:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 912.24µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:04:21Z" - latency: 1.792204ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:04:21Z" - latency: 831.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:03:21Z" - latency: 1.720056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:03:21Z" - latency: 953.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:02:21Z" - latency: 1.557338ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:02:21Z" - latency: 892.465µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:01:21Z" - latency: 1.837982ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:01:21Z" - latency: 734.569µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T19:00:21Z" - latency: 1.670124ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T19:00:21Z" kind: List metadata: resourceVersion: ""