Jason DeTiberus
Jason DeTiberus
>  > Whoah, this is interesting - we keep the CPU busy while squashing. On one hand - good, on the other hand - maybe there is some...
If I'm reading the overlapping of these graphs correctly, then pretty much the entire cpu chart for the represented builds are totally consumed by the docker pull, squash and docker...
There is a similar issue tracked against CAPA here: https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/969 I do think this is something that we should probably validate and try to guard against in CAPI rather than...
@liztio we should probably ensure that we are validating this as part of the validating webhooks work you are doing.
> This issue seems mostly a documentation / infrastructure limitation, @detiber thoughts? It depends? The issue is complicated quite a bit by the kubernetes cloud provider integration, which requires a...
/lifecycle frozen
Here is a very basic kustomize config that you can use for validation: ```yaml # yaml-language-server: $schema=https://json.schemastore.org/kustomization --- apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - namespace.yaml - my/deployment.yaml namespace: demo ```
> You have a point here, although I would classify this as an enhancement request. > > The main problem is that some tools expose some configuration variables only using...
> By the way, this is one of the reasons why we switched to Bash arrays to dynamically compose commands. So maybe the solution is to provide something along those...