On Wed, Jun 7, 2017 at 1:33 AM, Giuseppe Scrivano wrote:
> Spyros Trigazis writes:
>
>> If we move to system containers, which containers we need to use?
>> Is ti recommended to maintain our own container images based on [2]?
>
> It will be better if we get only one version that we can all use.
Spyros Trigazis writes:
> If we move to system containers, which containers we need to use?
> Is ti recommended to maintain our own container images based on [2]?
It will be better if we get only one version that we can all use. We
don't have the kube images in atomic-system-containers yet but
On 06/06/2017 10:49 AM, Spyros Trigazis wrote:
> Hello,
>
> I'm working on using system containers for our kubernetes configuration.
>
> What I found a little strange in a solution like [1], is that we don't specify
> the version of the component. eg if i do atomic install --system
> jasonbroo
On Tue, Jun 6, 2017 at 7:49 AM, Spyros Trigazis wrote:
> Hello,
>
> I'm working on using system containers for our kubernetes configuration.
>
> What I found a little strange in a solution like [1], is that we don't
> specify
> the version of the component. eg if i do atomic install --system
> jas
Hello,
I'm working on using system containers for our kubernetes configuration.
What I found a little strange in a solution like [1], is that we don't
specify
the version of the component. eg if i do atomic install --system
jasonbrooks/kubernetes-kubelet:rawhide
I don't control and I don't know t
Hi Jason,
I tried etcd from your branch [2] and with a single change [1], the etcd
system container was a drop-in replacement instead of using etcd
from the package.
Cheers,
Spyros
[1] I needed to set ETCD_INITIAL_CLUSTER="" since we use
the option ETCD_DISCOVERY and they conflict.
ETCD_INITIAL_
Hi Jason,
Jason Brooks writes:
> I've experimented w/ making more changes to the ansible like these --
> adapting the scripts to the system containers rather than the reverse,
> but I started thinking it'd be easier to adapt the system containers
> to be more of a drop-in replacement, leaving th
On Tue, May 2, 2017 at 1:06 AM, Giuseppe Scrivano wrote:
> Hi,
>
> Great work Jason! We should definitely get these images into
> atomic-system-containers.
>
> Daniel Walsh writes:
>
>> If these config changes should be in the standard etcd/flanneld
>> containers please open pull requests to fix
Hi,
Great work Jason! We should definitely get these images into
atomic-system-containers.
Daniel Walsh writes:
> If these config changes should be in the standard etcd/flanneld
> containers please open pull requests to fix this on
> github.com:projectatomic/atomic-system-containers
>
> On 04/
If these config changes should be in the standard etcd/flanneld
containers please open pull requests to fix this on
github.com:projectatomic/atomic-system-containers
On 04/28/2017 03:08 PM, Jason Brooks wrote:
On Fri, Apr 28, 2017 at 1:05 AM, Spyros Trigazis wrote:
Hi,
So far, I have only t
On Fri, Apr 28, 2017 at 1:05 AM, Spyros Trigazis wrote:
> Hi,
>
> So far, I have only tried etcd, works well but the only piece missing is
> a way to pass TLS credentials which is quite important for certain
> deployments like ours. My next goal is flannel. Flannel will require
> TLS creds as well
Hi,
So far, I have only tried etcd, works well but the only piece missing is
a way to pass TLS credentials which is quite important for certain
deployments like ours. My next goal is flannel. Flannel will require
TLS creds as well. To do it, I rebuilt the image to bindmount them.
To be honest, I
12 matches
Mail list logo
