#1 Track kubernetes system container builds
Opened by strigazi. Modified

In this issue we can track all the updates we do for the kuberntes system containers.

registry.fedoraproject.org/f25/kubernetes-apiserver
registry.fedoraproject.org/f25/kubernetes-controller-manager
registry.fedoraproject.org/f25/kubernetes-scheduler
registry.fedoraproject.org/f25/kubernetes-kubelet
registry.fedoraproject.org/f25/kubernetes-master
registry.fedoraproject.org/f25/kubernetes-node

We need to track the above to know when they were built and with which commit from:
https://github.com/projectatomic/atomic-system-containers


@jasonbrooks Can you add the current state?

If there is a better way to track these changes we can abandon this issue.

@strigazi - could we use skopeo and generate a static web page every X minutes?

skopeo inspect docker://registry.fedoraproject.org/f25/kubernetes-apiserver 
{
    "Name": "registry.fedoraproject.org/f25/kubernetes-apiserver",
    "Digest": "sha256:a80bc93eabda94fc8fd9fb41a6cc915204aca6170abd9c6fe3b42bb9a65a9dbd",
    "RepoTags": [
        "0.1-3.f25docker",
        "0.1",
        "latest",
        "0.1-6.f25docker",
        "0.1-8.f25docker",
        "0.1-9.f25docker",
        "0.1-12.f25container",
        "0.1-13.f25container",
        "0.1-15.f25container"
    ],
    "Created": "2017-06-27T17:33:19.31502Z",
    "DockerVersion": "1.10.3",
    "Labels": {
        "Architecture": "x86_64",
        "BZComponent": "kubernetes-apiserver",
        "Name": "f25/kubernetes-apiserver",
        "RUN": "/usr/bin/docker/ run -d --net=host -p 443:443",
        "Release": "15.f25container",
        "Version": "0.1",
        "architecture": "x86_64",
        "authoritative-source-url": "registry.example.com",
        "build-date": "2017-06-27T17:21:40.082642",
        "com.redhat.build-host": "osbs-node02.phx2.fedoraproject.org",
        "com.redhat.component": "kubernetes-apiserver",
        "distribution-scope": "private",
        "name": "f25/kubernetes-apiserver",
        "release": "15.f25container",
        "run": "/usr/bin/docker/ run -d --net=host -p 443:443",
        "vcs-ref": "e344606a01f8d15f3eac96ffd01718ff2f814d39",
        "vcs-type": "git",
        "vendor": "Fedora Project",
        "version": "0.1"
    },
    "Architecture": "amd64",
    "Os": "linux",
    "Layers": [
        "sha256:6f52cfd828e2225d7b4a71168a8c066cf4756655e94ad127cc83d04e2184d990",
        "sha256:0d7d09d33d23bd3ab64e140271baa1db2252aab3f99a12fd06a973aec894da42",
        "sha256:af8cc95aeb6903a82ae4ae34bef6a0fe3bca6b02dcd8bb27471e10e950e095f9"
    ]
}

@dustymabe The commit from [1] is:
"vcs-ref": "e344606a01f8d15f3eac96ffd01718ff2f814d39" ?

[1] https://github.com/projectatomic/atomic-system-containers

I think that is from the dist-git repo [1]

[1] https://src.fedoraproject.org/cgit/container/kubernetes-apiserver.git/commit/?id=e344606a01f8d15f3eac96ffd01718ff2f814d39

The static webpage would be awesome and extremely helpful.

And since we can check what is in from [1] that is good.

But we need a kind of sync between [1] and [2]. Outsider can contribute to [1], but if you don't mind the extra load, it is fine for me.

[1] https://src.fedoraproject.org/cgit/container/kubernetes-*
[2] https://github.com/projectatomic/atomic-system-containers

As I understand it, @maxamillion updates/releases the container images roughly every two weeks, so if the current stable version in of kube in fedora is older than that, the container images should have it.

The images don't list their packages' version number, because lacking a way to automatically ensure that the image version matches the rpm version, we've been marking our images version 0. We could start manually setting the version number on the kubernetes images for now, though.

Another thing that comes to mind is that 1.5.x isn't maintained any more by the upstream, and another is that while 1.5.3 is the stable fedora package, 1.5.7 (from apr) was the last 1.5.x version.

I don't know if we care to make f25's kube the last 1.5.x release, or if we should upgrade it to 1.5.7, or if we should just ignore it all together.

And then there's f26 -- there don't appear to be any kube f26 container images yet. I don't know if f26 container images have started up yet?

I don't know if we care to make f25's kube the last 1.5.x release, or if we should upgrade it to 1.5.7, or if we should just ignore it all together.

my preference would be to ignore, mainly because I am focused on atomic host. There may be some people interested in maintaining kube for fedora 25, but let's let them surface before we put effort there

And then there's f26 -- there don't appear to be any kube f26 container images yet. I don't know if f26 container images have started up yet?

I think the f26 container images should be in the next FLIBS release

Metadata