Polyaxon Community Edition is based on Polyaxon’s open-source project, and it deploys on a single cluster and a single namespace, there’s no limitation on the number of nodes you can use. The deployment comes with an in-cluster agent deployment for managing workload.
The best way to deploy and try Polyaxon is to keep the default
ClusterIp service type,
polyaxon port-forward command to expose the API and dashboard on your localhost in a secure way,
the command will auto-configure the client and the cli for future interactions:
polyaxon admin deploy ...
If you wish to expose your Polyaxon deployment to several users, each user can port-forward the traffic to localhost, or you can also spend some time to configure a load balancer or ingress.
Polyaxon Community Edition manages the operator and the gateway in a single deployment, and they must be enabled, please do not disable these services:
Note: This is the default configuration of the chart, you do not need to add this to your deployment config file.
Polyaxon API can be easily scaled horizontally if you have a growing traffic, but you are submitting a large number of operations, and you think that you can benefit from using a background worker, you can enable the open-source scheduler to process events and submission in an asynchronous fashion.
Note: By default, the scheduler is disabled, you should only enable it after scaling the API service.
Note: You can have more control about the broker, please check this guide.
You need to configure the connections to authorize for the platform. Please check connections section.
The community UI is an optional free tool that can be used to view information about your jobs and services, it’s enabled by default for all deployments.
If your main use of Polyaxon is to schedule jobs, use the packaging format, and interact with the platform using the CLI/Client/APIs, you can disable the UI:
Polyaxon will deploy by default using a ClusterIp service, and provides a command to port-forward the traffic to localhost in a secure way. If you decide to deploy Polyaxon CE using a LoadBalancer or an Ingress, we strongly recommend that users only use environments they control by locking the deployment down at the network level.