Boosting Arm64 Support in CNCF Projects with OCI Credits
The rise of Arm64 architecture in cloud services presents a significant opportunity for CNCF projects. By improving support for Arm64, you can enhance performance and reduce costs. OCI credits from Oracle Cloud provide a pathway to utilize these resources, making it easier for maintainers to adopt this architecture in their workflows.
To get started with OCI credits, maintainers need to submit a CNCF Service Desk ticket detailing their intended use, the OCI services they plan to utilize, and a rough estimate of their usage. The CNCF Infra team assists in provisioning Arm64 instances of various sizes, which can be used as self-hosted GitHub Actions runners. This flexibility allows teams to tailor their CI/CD pipelines to leverage the benefits of Arm64.
However, there are important considerations to keep in mind. The CNCF Infra team imposes reasonable guardrails to ensure sustainability and fair access to these shared resources. Initially, they recommend limiting resource spending to under $5,000 USD per month, although exceptions can be made based on actual needs. Understanding these limitations will help you plan your project effectively and avoid unexpected costs.
Key takeaways
- →Submit a CNCF Service Desk ticket to access OCI credits for Arm64 resources.
- →Utilize OCI credits to provision Arm64 instances as self-hosted GitHub Actions runners.
- →Limit resource spending to under $5,000 USD/month initially to ensure sustainability.
- →Collaborate with the CNCF Infra team for optimal provisioning of resources.
Why it matters
Improving Arm64 support can lead to better performance and cost efficiency in cloud-native applications, making it crucial for modern infrastructure.
When NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsUnified observability — logs, uptime monitoring, and on-call in one place. Used by 50,000+ engineering teams to ship faster and sleep better.
Try Better Stack free →Runtime Supply Chain Verification with NRI: Securing Your Kubernetes Deployments
In a world where supply chain attacks are rampant, ensuring the integrity of your container images is crucial. The Node Resource Interface (NRI) allows you to enforce supply chain verification at runtime, leveraging plugins to validate image attestations before they even start. Dive into how this mechanism works and what you need to watch out for in production.
Why Your Controller's Cache Keeps the API Server Running Smoothly
Ever wonder how your Kubernetes controller can handle hundreds of calls per second without crashing the API server? The secret lies in the controller-runtime's local cache mechanism, which uses a combination of informers and stores to optimize data access. Dive in to understand the mechanics behind this powerful feature.
Stop Your Kubernetes Health Checks from Waking Services: Here’s How
Kubernetes health checks can inadvertently trigger your services to scale up when they should remain idle. Learn how to leverage the ProbeResponse feature to manage health checks effectively and keep your services scaled to zero when not in use.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.