Polyaxon provides a very flexible schema for defining connections, with the possibility to attach a secret and/or a config map.

In this release we extended the connection schema with two additional fields:

  • annotations: Allows defining a list of annotations to always use with the connection.
  • env: Allows defining a list of environment variables to always inject with the connection.

Connection schema with annotations

In some cases, users prefer to define a connection schema using the IAM role instead of a secret. In such case they need to reference the role name in an annotation.

With this new improvement, admins can define the artifacts store or the connection using the new annotations field:

  name: artifacts
  kind: s3
    bucket: "s3://bucket/"
  annotations: myapp-iam-role

Connection schema with environment variables

Previously, when users defined a connection with a secret that gets mounted as a volume and needed some additional environment variables, they had to create an additional config map, In this release, users can use the new env field on the connection schema to instruct Polyaxon to always use the environment variables whenever the connection is requested:

  - name: connection-name
    kind: ...
    schema: {...}
      name: "my-secret"
      key1: "value1"
      key2: "value2"

Learn More about Polyaxon

This blog post just goes over a couple of features that we shipped in v1.18. To learn more about all the features, fixes, and enhancements, please visit the release notes and the short term roadmap.

Polyaxon continues to grow quickly and keeps improving and providing the simplest machine learning abstraction. We hope that these updates will improve your workflows and increase your productivity, and again, thank you for your continued feedback and support.