In the context of #391 we had stumbled about a very specific problem how to best update resources which leads to multiple discussions (see zalando/restful-api-guidelines#391 (comment) and https://github.bus.zalan.do/Sokoban/rutherfordium/pull/17#discussion_r551990) including the API guild meeting.

The core discussion can be summarized by POST vs. `

Expected Behavior

When you have 2 HorizontalPodAutoscalers using annotations to specify the prometheus server (e.g. metric-config.external.prometheus-query.prometheus/prometheus-server: http://my-prometheus), metrics should be read from the prometheus server in the annotation.

Actual Behavior

The prometheus-server defined in the kube-metrics-server flags is used instead of using t

• how to setup the tools stackset-controller + skipper + optional RBAC
• how to use from user point of view (explain traffic) or write a small kubectl plugin stack
• how to create a development environment

During our Innovation Camp, I discovered that we don't prefix anything, therefore usage of CSS Functions like transform3D are not applicable and might create a breaking UI.

As we now have publicly available release and snapshot artifacts we should update and extend the "user guide".