apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31661" uid: 4b4ebe84-8275-4c9a-b7d7-73f585eb7c2c spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T18:04:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 926.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 810.517µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 948.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 1.024669ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 891.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 982.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:34:30Z" - latency: 800.221µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:33:30Z" - latency: 793.062µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:32:30Z" - latency: 1.089976ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:31:30Z" - latency: 817.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31663" uid: de8fd876-7b7e-4d31-bd90-7b836d566bd6 spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:03:30Z" message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.987941ms message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 7.967196ms message: 'load-balancer-api-external: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:39:30Z" - latency: 4.176046ms message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 8.406281ms message: 'load-balancer-api-external: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:38:30Z" - latency: 5.050074ms message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 7.854341ms message: 'load-balancer-api-external: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:37:30Z" - latency: 4.8521ms message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 11.306196ms message: 'load-balancer-api-external: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:36:30Z" - latency: 4.767476ms message: 'load-balancer-api-external: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 8.218286ms message: 'load-balancer-api-external: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:35:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31662" uid: 4df965c8-0a57-4f21-9f93-df8f48072d6f spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T18:03:30Z" message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.974435ms message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 7.923339ms message: 'load-balancer-api-internal: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:39:30Z" - latency: 4.170299ms message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 8.431932ms message: 'load-balancer-api-internal: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:38:30Z" - latency: 5.062444ms message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 7.813833ms message: 'load-balancer-api-internal: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:37:30Z" - latency: 5.836069ms message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 11.277403ms message: 'load-balancer-api-internal: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:36:30Z" - latency: 4.823328ms message: 'load-balancer-api-internal: tcp connection to af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 8.168061ms message: 'load-balancer-api-internal: resolved host name af7a9960610404d1592f358d190c0acc-d3fe32791b7089ba.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:35:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-131-177 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31660" uid: 918a55c4-15da-46c7-a636-6a139147d701 spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:30Z" message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.181777ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 2.146082ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 2.243316ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 2.453809ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 2.19767ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 2.363315ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:34:30Z" - latency: 2.419075ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:33:30Z" - latency: 2.451379ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:32:30Z" - latency: 2.104881ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:31:30Z" - latency: 2.123663ms message: 'network-check-target-ip-10-0-131-177: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-133-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31659" uid: 73539001-a8ad-4c09-8c2f-05551871a684 spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:30Z" message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.075362ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 1.783422ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 2.170567ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 1.982755ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 2.192393ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 2.06418ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:34:30Z" - latency: 2.32008ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:33:30Z" - latency: 2.193376ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:32:30Z" - latency: 2.164582ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:31:30Z" - latency: 2.105685ms message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-ip-10-0-136-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31657" uid: ee8f6e61-c143-4107-abc9-190306f96937 spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:04:30Z" message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186168ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 792.032µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 1.282074ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 882.776µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 1.352744ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 811.112µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:34:30Z" - latency: 823.329µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:33:30Z" - latency: 778.471µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:32:30Z" - latency: 1.244655ms message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:31:30Z" - latency: 834.505µs message: 'network-check-target-ip-10-0-136-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:30:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:57:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-172-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-172.ec2.internal uid: 7abe13bd-9692-4be0-b056-e660c75c5c5b resourceVersion: "31658" uid: f10b5db5-8c83-41e4-9195-8c60ea9e58d8 spec: sourcePod: network-check-source-8894fc9bd-pchtp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T18:03:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 761.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:39:30Z" - latency: 1.429811ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:39:30Z" - latency: 866.063µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:38:30Z" - latency: 1.492711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:38:30Z" - latency: 1.005776ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:37:30Z" - latency: 1.789444ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:37:30Z" - latency: 1.165543ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:36:30Z" - latency: 1.679241ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:36:30Z" - latency: 757.527µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:35:30Z" - latency: 1.735876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:35:30Z" kind: List metadata: resourceVersion: ""