apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "38560" uid: 364af1c9-e4ad-4be5-9b50-7950d45e4c74 spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T18:48:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.136621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:04Z" - latency: 1.342985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:04Z" - latency: 1.422391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:04Z" - latency: 983.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:04Z" - latency: 1.167828ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 1.054687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 1.505865ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 1.396109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 1.174966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 1.216136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "35135" uid: d3946dd0-b6a2-47ab-9dd6-cb592ed6bda5 spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:47:04Z" message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.907423ms message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 11.233518ms message: 'load-balancer-api-external: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:04Z" - latency: 5.652265ms message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 7.059796ms message: 'load-balancer-api-external: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:04:04Z" - latency: 5.306146ms message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 6.164322ms message: 'load-balancer-api-external: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:03:04Z" - latency: 5.204116ms message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 11.201645ms message: 'load-balancer-api-external: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:02:04Z" - latency: 5.213868ms message: 'load-balancer-api-external: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 9.342911ms message: 'load-balancer-api-external: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "35136" uid: 1fb5142e-a1cc-4cde-9f7f-4dee3308064a spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T18:47:04Z" message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.882623ms message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 11.157333ms message: 'load-balancer-api-internal: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:04Z" - latency: 5.626088ms message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 7.267955ms message: 'load-balancer-api-internal: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:04:04Z" - latency: 5.282827ms message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 7.004616ms message: 'load-balancer-api-internal: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:03:04Z" - latency: 5.152575ms message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 11.221499ms message: 'load-balancer-api-internal: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:02:04Z" - latency: 4.659942ms message: 'load-balancer-api-internal: tcp connection to a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 8.73777ms message: 'load-balancer-api-internal: resolved host name a4b7c5e78a2224c7fa9e809d68083e50-e41dd2c45f21093e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-129-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "38558" uid: aca69a30-3d96-42f7-8ed5-b31af7d9f59b spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:48:04Z" message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.738294ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:04Z" - latency: 1.940922ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:04Z" - latency: 1.767969ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:04Z" - latency: 1.937285ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:04Z" - latency: 1.717412ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 1.856406ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 2.222361ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 1.929779ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 1.87814ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 2.007065ms message: 'network-check-target-ip-10-0-129-26: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-132-151 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "38557" uid: aa061e31-431b-49d4-be7a-580fd401ada2 spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:48:04Z" message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 916.473µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:04Z" - latency: 1.518624ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:04Z" - latency: 1.538417ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:04Z" - latency: 883.64µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:04Z" - latency: 801.197µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 1.109425ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 1.431023ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 888.927µs message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 1.055889ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 1.775967ms message: 'network-check-target-ip-10-0-132-151: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-ip-10-0-139-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "38559" uid: 9bf4666a-6c76-4b48-b8c1-7a91e3ba7885 spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T18:48:04Z" message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.034858ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:09:04Z" - latency: 2.224326ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:08:04Z" - latency: 2.294332ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:07:04Z" - latency: 2.100438ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:06:04Z" - latency: 2.349425ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 2.659545ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 2.107007ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 2.297039ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 2.193946ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 2.199626ms message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:00:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T18:41:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-151-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-151.ec2.internal uid: c37fc2f6-1222-4ca4-811f-30560a2db08b resourceVersion: "35134" uid: 3c54740f-a9fc-4a68-88b0-862532197b8c spec: sourcePod: network-check-source-8894fc9bd-bw86q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T18:47:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 879.814µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:05:04Z" - latency: 2.136901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:05:04Z" - latency: 859.971µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:04:04Z" - latency: 2.047095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:04:04Z" - latency: 906.599µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:03:04Z" - latency: 1.992761ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:03:04Z" - latency: 837.886µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:02:04Z" - latency: 1.689267ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:02:04Z" - latency: 732.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T19:01:04Z" - latency: 2.627521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T19:01:04Z" kind: List metadata: resourceVersion: ""