Karl Schriek

True, if that were the only reason why we want to avoid App-of-Apps then a templating approach could solve it, and you are right to point that out. In this...

@crenshaw-dev thanks, I have not come across those two issues before. The topic seems to be already quite splintered, so my apologies for opening up yet another one. #7437 seems...

I would actually like to see the ability to explicitly define dependency between two applications. E.g.: App1 doesn't depend on anything: ``` apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: App1 spec:...

As a bit more context, we have the following TLS certificates, i.e. mydomain.com and login.mydomain.com are on the same cert. But foo.mydomain.com is on a separate cert. This is the...

We are running into this on 1.14.0 as well. We use `templatefile` to render manifests before we pass them to ``` resource "kubectl_manifest" "this" { yaml_body = templatefile( "${local.templates_path}/my-app.tftpl", {...

There is only one commit between 1.13.1 and 1.14.0 though. The two features that were added (`apply_only` and `force_conflicts`) I think are unlikely to have caused this. As a side-effect...

As far as I can see, the `values` field isn't even used. The `ml-metadata` Artifact signature `kubeflow.org/alpha/metrics` that is relevant here doesn't have a `values` property. Also the under the...

Ok, now I see! The entire `self.__dict__` gets converted to string. Thanks for the explanation

@PatrickXYS, @Jeffwan

Yes, that is the conclusion I came to as well. Doesn't look like it would be too hard to implement though? Essentially instead of creating the config maps as it...