Hi Imesh,
That's what I was looking for.
Before this solution, to avoid creating as many docker images as
environments and components, and taking into account the current limit
(https://github.com/wso2/kubernetes-apim/issues/15), I planned to use the
solution
Hi All,
It seems that Kubernetes ConfigMaps can be used for managing product
configurations without having to build Docker images for each pattern with
specific configurations. This was recently tested with Enterprise
Integrator and its K8S resources used can be found below:
[Adding Chamila]
On Mon, Sep 4, 2017 at 2:36 PM, Niranjan Karunanandham
wrote:
> Hi Chamila,
>
> On Fri, Sep 1, 2017 at 9:57 AM, Chamila De Alwis
> wrote:
>
>> Hi,
>>
>> Please find the meeting notes below.
>>
>> 1. The existing approach where resorting to
Hi Chamila,
On Fri, Sep 1, 2017 at 9:57 AM, Chamila De Alwis wrote:
> Hi,
>
> Please find the meeting notes below.
>
> 1. The existing approach where resorting to the deployment.yaml file to
> figure out lookup hierarchy would be dropped.
> 2. Instead, the lookup hierarchy
Agree. The completed description of how configuration lookup happens should
be properly documented, and our production guidelines should contain the
recommendations for each deployment scenario.
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
On Mon, Sep 4, 2017 at 11:25 AM, Chamila De Alwis wrote:
> Hi Bhathiya,
>
> Yes, this is an important point. However, I don't think we'd need to
> handle the order for the non-Container scenario specifically, as it would
> complicate the implementation too much. IMO config