These are all different loads and different origination dates. I'm guessing they were blocked for some reason by the mailing list, and unblocked by a moderator just now? -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar@windriver.com] Sent: Tuesday, January 21, 2020 1:52 PM To: cristopher.j.lemus.contreras@intel.com; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX platform-integ-apps docker images Make it stop! : ) -----Original Message----- From: cristopher.j.lemus.contreras@intel.com <cristopher.j.lemus.contreras@intel.com> Sent: Wednesday, January 15, 2020 4:09 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images List of docker images required for "platform-integ-apps": BUILD_ID="20200115T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss