Govern node jointly used with API node and/or Automation node

Gabriel

Hi everyone

My setup is the following:

• Design Node
• Deployer Node
• Automation Node
• API Node
• Govern Node

Each node is a separate instance (e.g the deployer node is remote to the design node). I recently setup a govern node with which I track all bundles deployed on the automation node, as well as all APIs deployed to the api node. There is a setting that prevents you from deploying a bundle/api if it was not signed-off previously on the govern node. This setting is outlined here at the very top. I was able to use this setting as long as I used a local deployer, but once I switched over to a remote one, the setting disappeared. Is this intended behaviour or am I missing a particular configuration?

Thanks in advance,

Gabriel

---

Operating system used: Alma Linux

fsergot

Hello @Schiggy
,

Can you ensure you have the govern activated on the Deployer node and that you refreshed your browser after that check is saved?

Thanks

Gabriel

Hi @fsergot
, thanks for your reply!

I activated the govern node on both, the deployer and automation node (although I think on the deployer is sufficient). The governable items section on the govern node even gets populated with projects.

What I did so far:

• Setup the different nodes
• Declared a nodeid for every node
• Created an API key on the govern node for the design, deployer, and automation node.
• Setup infrastructure (using the automation node) on the deployer node.
• Successfully deployed project bundles to the automation node.

fsergot

That seems weird indeed. the display of the Dataiku Govern Policy is only driven by the activation of the govern integration on the Deployer node, nothing else (and even if the integration itself is not working, the dorp down is still available).

Which version are you using?

Gabriel

After almost 24h the dropdown appeared in the GUI of both, the automation node and the api node. This is odd "> Well, it apparently works now. Thanks for your time, I greatly appreciate it.

catten92

Hey Gabriel,

I saw your post about the Govern node and the setup you have. We have the exact same setup by us and I would like to know if you only govern projects on the automation node or already when they are on the design node and how do you manage this process?

I would appreciate if you can share your experience with me.

Best regards,

Christophe

Gabriel

Hi Christophe

Frankly, we haven't used the Govern Node in production yet. I only installed it for trial purposes and to fully understand its capabilities. However, I don't think it is sensible to track every project on the design node, since that inhibits its agile nature. Once a project is mature enough and is planned to enter the MLOps cycle, then the admin overhead (and the advantages such as following a RAFT framework, progress overview, etc. that come with it) seems justified.

Greetings from Switzerland,

Gabriel

catten92

Hey

Thank you for your feedback. I am also currently trying to understand all its capabilities and integration into our workflows.

However, my idea was slightly different. I wanted to manage every project on the design node from the beginning and regroup them into business initiatives (business initiatives = teams by us). In this way, the team leader has an overview of all his projects and their status, the manager of several teams sees all the projects of his teams, and so on... The sign-off people (validators, IT, ...) will have access to all the projects.

However, the concept of the integration of the design and automation node within the govern node is still a part I haven't understood yet. To me, a project should be governed on the design node before it goes into production (hence the automation node) and then on the automation node the bundle should be automatically governed when the project is governed on the design node. But this is as far as I understand not the case at the moment, as the project is appearing seperatly on the govern node again,or am I missing something?

Greetings from Luxembourg,

Christophe