Private GKE with restricted access to cluster master endpoints
A guide to private Google Kubernetes Engine cluster with different level of restricted access to cluster master endpoints
What is the definition for releases that are Alpha, Beta, and GA?
This is a description that varies from company to company. We decided to publish what each one of these release definitions are for Armory, and where we suggest you install them.
Application is working and installation works, but some functionality is likely to be missing and a number of known and unknown bugs are likely to surface. We also call this a private beta, as it is released to a limited audience.
Not production! No really don’t do it, this release is meant to give the user an advanced ability to get to know the platform sooner, but also to give us feedback on what is working and not working. Alpha is meant for a closed development environment, or a learning environment that can be destroyed at any minute and rebuilt.
Application is working and installation works, has had all of the major known issues fixed, but has not been tested with enough customers. Also known as open beta release. It is much closer to what we expect to ship to our audience.
Pretty much everywhere except production. A production installation could occur but proceed with caution, and have proper rollbacks ready. Recommended is your development, QA, staging, or pre-prod environments. This release is meant to give the user an advanced ability to set up new functionality and hit the ground running when GA releases. It is also to give feedback on any final major issues.
All major technical issues have been identified and/or resolved. The application is available for install by all customers.
Anywhere you like.
With the above understanding jump over to our documentation and enjoy. https://docs.armory.io/release-notes/