Private registry for docker images

[brunowego]

Private registry for docker images

[mmourafiq]

I think this the right approach, may be to make it a bit simpler than a command line is to use yaml file. Doing this in the chart is just extra logic to maintain that does not yield too much benefit for most users, and it will be a bit confusing if the chart start using other subcharts that don't follow this convention.

[brunowego]

I understand. Thanks @mouradmourafiq

[brunowego]

To prevent broken the API with who already are using this chart, perhaps just only add global.imageRegistry and global.imagePullSecrets.

[mmourafiq]

@brunowego can't this be done directly using the values on the config.yaml during the deployment time?

[brunowego]

Yes! I'm using something like this:

helm install polyaxon/polyaxon \
  -n polyaxon \
  --namespace polyaxon \
  --set serviceType=ClusterIP \
  --set ingress.enabled=true \
  --set ingress.hostName=polyaxon.company.com \
  --set user.username=brunowego \
  --set [email protected] \
  --set user.password="$(openssl rand -hex 32)" \
  --timeout 900 \
  --wait \
  -f <(cat << EOF
api:
  image: registry.company.com:5001/polyaxon/polyaxon-api

streams:
  image: registry.company.com:5001/polyaxon/polyaxon-streams

scheduler:
  image: registry.company.com:5001/polyaxon/polyaxon-scheduler

hpsearch:
  image: registry.company.com:5001/polyaxon/polyaxon-hpsearch

eventsHandlers:
  image: registry.company.com:5001/polyaxon/polyaxon-events-handlers

k8sEventsHandlers:
  image: registry.company.com:5001/polyaxon/polyaxon-k8s-events-handlers

beat:
  image: registry.company.com:5001/polyaxon/polyaxon-beat

crons:
  image: registry.company.com:5001/polyaxon/polyaxon-crons

eventMonitors:
  namespace:
    image: registry.company.com:5001/polyaxon/polyaxon-monitor-namespace

  statuses:
    image: registry.company.com:5001/polyaxon/polyaxon-monitor-statuses

resourcesDaemon:
  image: registry.company.com:5001/polyaxon/polyaxon-monitor-resources

hooks:
  image: registry.company.com:5001/polyaxon/polyaxon-manage

tablesHook:
  image: registry.company.com:5001/polyaxon/polyaxon-tables

postgresql:
  image: registry.company.com:5001/library/postgres
  metrics:
    image: registry.company.com:5001/wrouesnel/postgres_exporter

redis:
  global:
    imageRegistry: registry.company.com:5001

rabbitmq-ha:
  image:
    repository: registry.company.com:5001/library/rabbitmq
  busyboxImage:
    repository: registry.company.com:5001/library/rabbitmq

docker-registry:
  image:
    repository: registry.company.com:5001/library/registry
EOF
)

[brunowego]

Or short way, only for polyaxon images:

helm install polyaxon/polyaxon \
  -n polyaxon \
  --namespace polyaxon \
  -f <(helm inspect values polyaxon/polyaxon | sed 's|repo/image|registry.company.com/repo/image|') \
  --set serviceType=ClusterIP \
  --set ingress.enabled=true \
  --set ingress.hostName=polyaxon.company.com \
  --set user.username=brunowego \
  --set [email protected] \
  --set user.password="$(openssl rand -hex 32)" \
  --timeout 900 \
  --wait