-
Story
-
Resolution: Done
-
Medium
-
None
-
None
With the current design, kubernetes is not in a one-to-one relationship with PDP Subgroups. This causes issues with respect to spinning up new PDPs. For example, kubernetes may spin up additional PDPs due to excessive load, but PAP may assign them to a low-load PDP Subgroup.
To resolve this, the design should be changed so that kubernetes is in a one-to-one relationship with PDP Subgroups. However, this would entail classifying the PDPs in some way so that PAP knows to which PDP Subgroup they should be assigned. PDPs in different kubernetes clusters could report different PDP types (e.g., drools-type1, drools-type2) or they could report different supported policy types.
In addition, we need to resolve how hierarchical policy types are handled with respect to the "supported policy types".
- blocks
-
POLICY-2023 Re-synch of PAP and PDP when the supported policy type changes
- Closed
1.
|
XACML PDP change to add PDP Group | Closed | ah999m | |
2.
|
Drools PDP change to add PDP Group | Closed | jrh3 | |
3.
|
Apex PDP change to add PDP group | Closed | a.sreekumar | |
4.
|
PAP add support for PDP group in heartbeat | Closed | ramverma | |
5.
|
XACML PDP remove supported policy types | Closed | ah999m | |
6.
|
Drools PDP remove supported policy types | Closed | jhh | |
7.
|
Apex PDP remove supported policy types | Closed | a.sreekumar | |
8.
|
Removed supported types from PDP-STATUS message in policy models | Closed | ramverma | |
9.
|
OOM changes to add PdpGroup in config files of PDPs | Closed | jhh | |
10.
|
Code changes in drools-pdp to delay registration message until controllers are fully loaded | Closed | jhh | |
11.
|
Docker changes to add PdpGroup in config files of PDPs | Closed | jrh3 |