Repository navigation
Conversation
szuecs
added
the
major
|
Docker image "registry-write.opensource.zalan.do/teapot/skipper:2016a7550a4f8403ab6127399f0e82013cbbb20d" is not based on an approved base image. Any production deployment relying on this image will be blocked. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Zalando Container Registry namespace |
|
Docker image "registry-write.opensource.zalan.do/teapot/skipper:9adda5699086d3b4f31e97db9633c09dfa15b72f" is not based on an approved base image. Any production deployment relying on this image will be blocked. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Zalando Container Registry namespace |
|
Docker image "registry-write.opensource.zalan.do/teapot/skipper:fd3cbaed8e7951126a0764d5bade852943686393" is not based on an approved base image. Any production deployment relying on this image will be blocked. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Zalando Container Registry namespace |
fd3cbae to
61b67a0
Compare
|
Docker image "registry-write.opensource.zalan.do/teapot/skipper:61b67a068655eec2c8ed3ecc0aa01a21caf09bfa" is not based on an approved base image. Any production deployment relying on this image will be blocked. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Zalando Container Registry namespace |
| Routing: rt, | ||
| Flags: proxy.Flags(proxy.OptionsNone), | ||
| Metrics: &metricstest.MockMetrics{}, | ||
| EnableH2CBackend: true, |
There was a problem hiding this comment.
I think one of the old tests must be also updated
https://github.com/zalando/skipper/blob/master/skipper_h2c_test.go
schemes: h2:// h3:// will enforce http/2 and http/3 calls h2c,h2,h3 are all schemes inside the proxy and availble via eskip backend definitions. h2c,h2,h3 are required each to be enabled via proxy.Params. Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
┌──────────┬─────────┬─────────┬─────────┐ │ Protocol │ Req/sec │ p50 lat │ p99 lat │ ├──────────┼─────────┼─────────┼─────────┤ │ h2c │ 8,749 │ 0.84ms │ 2.16ms │ ├──────────┼─────────┼─────────┼─────────┤ │ h2 │ 8,296 │ 0.89ms │ 2.08ms │ ├──────────┼─────────┼─────────┼─────────┤ │ h3 │ 7,387 │ 0.97ms │ 2.36ms │ └──────────┴─────────┴─────────┴─────────┘ Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
…o enable it Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
…lear doc: fix typo Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
07b749c to
47ed91b
Compare
…ocol and pass Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
|
Docker image "registry-write.opensource.zalan.do/teapot/skipper:9203293db9dc71eeff7e994d2350eaacc2845633" is not based on an approved base image. Any production deployment relying on this image will be blocked. To create a compliant Docker image of your application, you must reference an allowed Docker image as its base image in your Dockerfile. This base image must come from the Zalando Container Registry namespace |
This branch has not been deployed
3 participants
"breaking" change: h2c:// needs to be enabled via proxy.Params or skipper.Options or
-enable-h2c-backendfeature: HTTP/2 support via h2:// scheme to backends needs to be enabled via proxy.Params or skipper.Options or
-enable-h2-backendfeature: HTTP/3 support via h3:// scheme to backends needs to be enabled via proxy.Params or skipper.Options or
-enable-h3-backendfeature: HTTP/3 support at the server handler on UDP network enabled via skipper.Options.EnableH3Server or
-enable-h3-serverfeature: dataclients/kubernetes support for h2:// and h3:// similar to already supported h2c