Skip to content

Releases: neuro-inc/neuro-extras

v23.7.0-1

06 Jul 20:41
Compare
Choose a tag to compare
cd: Change cluster for tests

23.7.0

06 Jul 20:25
2e3b972
Compare
Choose a tag to compare

What's Changed

Full Changelog: v22.2.2...v23.7.0

v22.2.2

17 Feb 15:22
Compare
Choose a tag to compare
Release v22.2.2

v22.2.1

10 Feb 11:02
Compare
Choose a tag to compare
Release v22.2.1

v21.11.5

25 Nov 16:47
22aacae
Compare
Choose a tag to compare
Release 21.11.5

v21.11.4

23 Nov 12:42
2c017a0
Compare
Choose a tag to compare
Release 21.11.4

v21.11.3

23 Nov 12:02
90acfee
Compare
Choose a tag to compare
Release 21.11.3

v21.11.2

23 Nov 11:19
abca0a1
Compare
Choose a tag to compare
Release 21.11.2

v21.11.1

23 Nov 10:46
873a912
Compare
Choose a tag to compare
Release 21.11.1

neuro-extras 21.11.0

23 Nov 10:28
df1df2a
Compare
Choose a tag to compare

Features

  • Allow to build and push docker images to the remote image registries.

    The requirement for allowing Kaniko (the underlying tool) to push such images - it should be authenticated.

    The registry authention data structure should be in the following form:
    {"auths": {"<registry URI>": {"auth": "<base64 encoded '<username>:<password>' string"}}}
    (tested with the https://index.docker.io/v1/ - public DockerHub registry)

    neuro-extras config build-registry-auth command might become handy in this case.

    To attach the target registry AUTH data into the builder job, one might save it as the platform secret and mount it into the builder job.
    Mounting of the secret could be done either as the ENV variable with the name prefixed by NE_REGISTRY_AUTH or as the secret file.
    In the latter case, the ENV variable should also be added with the mentioned above prefix and pointing to the corresponding file. (#328)