Sabby Anandan

This is already exposed in the producer side; we would have to add it to the Admin for provisioning.

@LakshmiLavanyaKasturi: Could we verify if this is already taken into account with docs.hiro.so nav-flow redo?

Update from today's pairing session with @obycode. We will absorb 1, 2, 8, 9, and 10 as part of the larger developer resources refresh initiative in Q3. Let's ignore them...

Relates to https://github.com/hirosystems/docs/issues/87.

This is a side effect from the new UI/UX around Task launches.

We already support it, though ([docs](https://docs.spring.io/spring-cloud-dataflow/docs/current/reference/htmlsingle/#spring-cloud-dataflow-stream-lifecycle-force-update)).

@thesoundofsilent: Can you expand and clarify what do you mean by "one or more pods are killed by kubernetes system pods like kube-system/calico-node-8xc5f", please? Any specific details as to the...

Hi, @SofaRabbit. My apologies for the delayed response. This is indeed a problem, but there's a workaround that you can by escaping the backslash. For example, when creating the definition...

Some notes from the internal discussion. 1) Perhaps we could create a new `@ConfigurationProperties` class that fully represents the app-level property overrides, including `createNodePort` and others along with the same...

Perhaps the option in the stream's force update via `--app-names` and `--force` flag may already address what you're looking for. WDYT?