kubernetes-apim
kubernetes-apim copied to clipboard
Add pattern-5 for NFS : pubstore, TM (1 & 2), KM, GW-Manager-Worker, Analytics (1 & 2)
Hi, With NFS, configuring GW is simpler. Only one POD: gw-manager-worker. This is scalable by simply increasing the value of the replication factor.
The same applies to apim-pubstore-tm1 and apim-pubstore-tm2 of the pattern-2, but by distributing the TM on other PODs. It is therefore relevant to remove the TM component from this PODs.
This is why I propose to create another pattern-5 from pattern-2 by :
- putting TM1 and TM2 on two other PODs.
- Keep only one POD : apim-pubstore
This is also beneficial from the operational point of view, the only three critical components for API consumption will be the two autoscalable POD:
- gw-manager-worker
- KM
And :
- TM1 & TM2
Thanks in advance. Youcef HILEM
Hi,
I have implemented this pattern and soon will be in production. The -Dprofile=traffic-manager option for tm1 and tm2 nodes is not used because the PODs do not start (classnotfoundexception is thrown).
Thanks Youcef HILEM
We might need to investigate and see why API-M is raising errors when it's started with Traffic Manager profile [1]. @yhilem really appreciate if you can share the logs that you got when this error was raised. Thanks!
[1] https://github.com/wso2/product-apim/blob/2.1.x/modules/p2-profile/product/pom.xml#L717