Arun S M
Arun S M
Note: For multi-cluster deployment, in order to do K8s authentication from multiple clusters, pods in those clusters shall authenticate with the Vault. The `env` parameter from the network deployment is...
Is the ask in this proposal to support Cactus deployment in Bevel?
I’ll confirm back on this. It was too complex to automate the workflow for orderer root CA refresh. However, peer mode refreshes should be good.
@nidhi-singh02 please check if there are inputs/learnings you can share with @mgCepeda.
@mbrandenburger most of these steps are covered in the feature developed. However, only place which I see edits are needed is the way configuration information is passed to the chaincode...
@manikanta-darsi please let me know if we can connect on this topic. I have the feature implemented but on older version of the codebase. My discord ID is arsulegai#7968 and...
Sure, having auth specific to cluster can help. The other concern is still on the GitOps, the repository information is at the organisation level, but the deployment shall happen across...
It would be nice if you can propose the schema with `k8s`, `gitops` models alongside an `organization`, we can iterate over that for more questions.
I meant to ask the scheme for the solution proposal. The current schema as can be seen, neither allow for one organisation to specify different release directories for different clusters,...
Sure, this should work as long as Kubernetes auth path is taken care.