Prune Sebastien THOMAS
Prune Sebastien THOMAS
Have the exact same issue here... Also, when using private repo + auth, we need to add to the Deployment Spec : ``` "imagePullSecrets": [ { "name": "your-auth-secret" } ],...
Will also work on a PR to support imagePullSecrets
The `ImagePullSecrets` can be set in a `ServiceAccount` as described in https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account Would it be a better solution to allow to set a `ServiceAccount` in the `etcdCluster` resource ?
made a PR for the `v` addition to the version : https://github.com/coreos/etcd-operator/pull/2079
issue referenced in - https://github.com/coreos/etcd-operator/issues/1974 - https://github.com/coreos/etcd-operator/issues/1960
Maybe doing this will make it harder to manage the upgrade process when only the image version is changed ? That would also imply an API change, while this PR...
maintaining .deb and .rpm is a waste of time. Build , unzip and you're done...
I do maintain large envs (using Ansible, really great, try it :) ) What I see is : using the repository of the distrib: - add the repository (and its...
I also had this issue with 2 apps using the same repo. As explained, restarting the `repo-server` and doing a `hard refresh` of the app resolved the issue. Before restarting...
@crenshaw-dev I'm still experiencing the issue in v2.9.3+6eba5be (without your patch, which I'm going to test) and I'd like to have this PR moving forward so I'm not running on...