Steven Hawkins

As a workaround you can use the src/main/kubernetes/kubernetes.yml fragment, instead of a config property: ``` apiVersion: apps/v1 kind: Deployment metadata: name: app-name spec: template: spec: containers: - name: container-name envFrom:...

We are looking at the best way to update the logging configuration at runtime - the configmap where these override values comes from need not exist. We need to have...

If I understand you correctly, that would look like: quarkus.kubernetes.env.optional-secrets=x,y,z quarkus.kubernetes.env.optional-configmaps=a,b,c quarkus.kubernetes.env.mapping.foo.optional=true Yes, I'm fine with that.

> it works just fine, doing the same on the above custom resource simply does nothing. @danpfe @rohanKanojia the logic is the same either way. I think there's a problem...

> I'm not sure if this would apply to all patch strategies. @manusa this issue only affects JSON patches when there is a context item and no item passed in...

> patchStatus() seems to works though Yes that is a json merge, not a json patch, so no diff is needed.

@manusa This commit shows a minimum amount of changes / breakage needed to non-generated files. The commit to the generated will be quite large, so I'm leaving that out for...

Thanks @rohanKanojia it turned out to be the go version. knative requires 1.18+. Updated to pare back where KubernetesResource is used - many of the locations where the object model...

@manusa @rohanKanojia A quick recap of the changes: - There are places that were mapping json and other types to Object and JsonNode, these have not changed - The places...

@andreaTP @manusa this introduces an AnyType class that is a base for IntOrString and RawExtension (which is still a KubernetesResource). Alternatively we could leave IntOrString alone and just introduce AnyType,...