k get pods
NAME READY STATUS RESTARTS AGE
apicast-apicast1-6cfd57dc87-bzx8j 1/1 Running 0 6m7s
apicast-apicast1-6cfd57dc87-m6mpm 1/1 Running 0 2m39s
apicast-apicast1-6cfd57dc87-xssj7 1/1 Running 0 2m39s
Add replicas to the Apicast CR with a value of 2
k patch apicast apicast1 --type merge --patch '{"spec":{"replicas": 2}}'
Check the deployment has 2 replicas
k get pods
NAME READY STATUS RESTARTS AGE
apicast-apicast1-6cfd57dc87-bzx8j 1/1 Running 0 12m
apicast-apicast1-6cfd57dc87-xssj7 1/1 Running 0 9m23s
As replicas are set explicitly in the CR, changes in the deployment will be reverted back. If we try to scale to 3 via the deployment
what
Implements https://issues.redhat.com/browse/THREESCALE-8754
replicas
field is setVerification steps
run env
Deploy apicast CR with no replica definition
Check that the Apicast CR does not have replicas in the CR
Wait for deployment to be available
Check the number of pods is 1
Scale to 3 via the deployment
Check the deployment has 3 replicas
Add
replicas
to the Apicast CR with a value of 2Check the deployment has 2 replicas
As replicas are set explicitly in the CR, changes in the deployment will be reverted back. If we try to scale to 3 via the deployment
The number of replicas will still be 2