-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
AMQ72 1.0.0.GA
-
None
It seem rather unfortunate from a user experience perspective creating new application from template and have 0 replicas set and no pod starting. Imho we should settle for some default like 2 for clustered deployment maybe?
templates git:(72-1.0-4) ✗ grep "name: AMQ_REPLICAS" -C 2 -R . ./amq-broker-72-persistence-clustered-ssl.yaml- - name: AMQ_CLUSTERED ./amq-broker-72-persistence-clustered-ssl.yaml- value: ${AMQ_CLUSTERED} ./amq-broker-72-persistence-clustered-ssl.yaml: - name: AMQ_REPLICAS ./amq-broker-72-persistence-clustered-ssl.yaml- value: ${AMQ_REPLICAS} ./amq-broker-72-persistence-clustered-ssl.yaml- - name: AMQ_CLUSTER_USER -- -- ./amq-broker-72-persistence-clustered-ssl.yaml-- description: Number of broker replicas for a cluster ./amq-broker-72-persistence-clustered-ssl.yaml- displayName: Number of Replicas ./amq-broker-72-persistence-clustered-ssl.yaml: name: AMQ_REPLICAS ./amq-broker-72-persistence-clustered-ssl.yaml- value: '0' ./amq-broker-72-persistence-clustered-ssl.yaml-- description: Clustered user -- -- ./amq-broker-72-persistence-clustered.yaml- - name: AMQ_CLUSTERED ./amq-broker-72-persistence-clustered.yaml- value: ${AMQ_CLUSTERED} ./amq-broker-72-persistence-clustered.yaml: - name: AMQ_REPLICAS ./amq-broker-72-persistence-clustered.yaml- value: ${AMQ_REPLICAS} ./amq-broker-72-persistence-clustered.yaml- - name: AMQ_CLUSTER_USER -- -- ./amq-broker-72-persistence-clustered.yaml-- description: Number of broker replicas for a cluster ./amq-broker-72-persistence-clustered.yaml- displayName: Number of Replicas ./amq-broker-72-persistence-clustered.yaml: name: AMQ_REPLICAS ./amq-broker-72-persistence-clustered.yaml- value: '0' ./amq-broker-72-persistence-clustered.yaml-- description: Clustered user