Xiang
Xiang
> Coming from the perspective of working on Amazon ECS, ingress feels widely applicable to many types of platforms and feels core to deploying many applications' Server components. To me,...
> To clarify: I should open a separate issue from this one to discuss the Ingress trait separately? Yes. In the spec repo: https://github.com/oam-dev/spec if you wish to add it...
> Something like node affinity would violate that we should translate to higher level abstraction, for example: 1. failure domain spreading (anti affinity) or SLA level (99% = one AZ;...
@Haishi2016 user cannot label node, which is the placement target. they can only express affinity between deployment units. that is why the SLA and deployment group can be useful.
@vturecek I agree that first one is important, but both metric format and the endpoint are needed. Then the external service can collect the metrics automatically from the given component.
We are working on one. /cc @resouer, @hongchaodeng
1 is ideal I think. I will try to come up with a better term :P
@vturecek @technosophos @resouer We currently solve this problem by running a couple of scripts inside the container to pipe the information as well as ensuring the ordering. Yes, it does...
/cc @resouer is this resolved?
> It seems to us that auth is fundamentally broken right now when used in conjunction with Kubernetes. When you want to do application-driven compaction, you almost assume that the...