How can we help?
Engine Yard Kontainers (EYK) is a Platform-as-a-Service (PaaS) for deploying and managing applications in containers. EYK runs application containers on a fully-managed Kubernetes infrastructure. It is designed to allow developers to shift from DevOps to NoOps, as they don’t need to spend additional time on deployments aside from a single code push command.
- Giving other users access to apps
- Problems running console commands when connected through 'eyk ps:console'
- How to open a console session to a running container within a pod
- Moving an application to a new cluster
- Setting the default browser when using EYK CLI on WSL
- Intermittent "Error 502 Service Temporarily Unavailable" errors following deployment
- Preventing deployment of broken apps to the EYK platform
- FAQs on Managing Microservices Architecture with EYK
- Setting healthchecks for an application
- How to forcefully terminate a pod
- Connecting an app to a Memcached service
- 'eyk ps' CLI command returns no 'web' processes
- Upgrading the eyk CLI tool
- "pre-receive hook declined" error while deploying an application to EYK
- Creating custom app-level or pod-level Grafana alerts/notifications
- Alert Rules and Notifications
- Preparing and Deploying an application to EYK using a Docker image
- Kibana Application Logging
- Introduction to Engine Yard Kontainers
- How Kontainers Works
- Deploy an Application with Kontainers
- Migrating from Engine Yard Cloud to Kontainers
- Managing Applications in Kontainers Web Console
- Configure Environment Variables with the Kontainers Web Console
- Scaling Applications with the Kontainers Web Console
- Security and Endpoint Administration in Kontainers
- Release Management with Kontainers
- Monitoring Applications on Kontainers
- Troubleshooting Applications on Kontainers
- Adding an S3 Bucket to a Kontainers Application