[update_containers] check custom images#3887
[update_containers] check custom images#3887karelyatin wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
Just for testing custom images for services. Signed-off-by: Yatin Karel <ykarel@redhat.com>
a9f4dda to
d79afc6
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/aa5fe3706c934b33ac8507ebb301d39d ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 05m 54s |
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi, httpd and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi, httpd and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi, httpd and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi, httpd and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
It's just for testing different frameworks like uwsgi, httpd and gunicorn, also old release with eventlet. Most probably will go with uwsgi same as what being tested upstream currently, but open to other frameworks which are being pushed upstream currently. The strategy in this patch being decided based on the container image. Depends-On: openstack-k8s-operators/ci-framework#3887 Related-Issue: #OSPRH-28742 Assisted-By: Claude Signed-off-by: Yatin Karel <ykarel@redhat.com>
Just for testing custom images for services.