Debugging Spinnaker Connectivity Issues with EKS Clusters Across VPCs: A Journey Through AWS Networking
In a recent debugging journey, we encountered a puzzling connectivity issue: our deployment tool, Spinnaker, which operates in a backend EKS cluster, suddenly lost access to resources in another cluster used for our public gateway. With recent EKS upgrades underway, we initially suspected a security group misconfiguration. However, this wasn’t a typical connectivity issue as no recent changes could clearly explain it.
As we investigated, we found ourselves navigating the complexities of AWS cross cluster routing and subnet configurations in EKS. Each clue pointed us deeper into the architecture, leading to unexpected discoveries about ENI placement and routing behavior within AWS. This blog details our journey through these layers of troubleshooting, the insights we gained, and the lessons learned along the way.
Balancing Acts: DynamoDB as a Rewards Ledger
Switching from AWS MSK with Confluent to MSK Serverless with Segmentio
Unleashing Imprint App’s asset management system to scale with new brand partners
How Imprint built a modern and robust banking mobile app
The evolution of Kubernetes resource management at Imprint
How Imprint built its card issuing platform in 6 months
As customer acquisition and retention costs skyrocket, branded card programs have become an emerging need for modern brands. Imprint’s first product to market, the branded rewards card, links to consumers’ bank accounts (just like Venmo or Coinbase), and comes without any baggage associated with traditional co-branded credit cards–no credit inquiries, no interest, and absolutely no fees. As of April 2022, we successfully launched 5 branded rewards cards, and we’re excited for what’s still to come.