Converting standard mode to dev mode on Kubernetes
You can convert your API Connect installation on Kubernetes from
standard mode to dev mode.
About this task
To review the installation modes, see Converting installation mode.
Procedure
Complete the following steps for each subsystem:
-
Use the following
apicupcommand to convert to Dev mode:# ./apicup subsys set [subsys-name] mode=dev # ./apicup subsys install [subsys-name] - Select one of the following actions, based on your deployment:
- If your Kubernetes deployment has two or more nodes, you do not have to remove replicasets. Continue to step 3
- If your Kubernetes deployment has only one node, you must remove replicasets. Complete the
following:
- Find the Helm release name and namespace for the subsystem that you are switching to dev
mode:
helm lsSample output:
NAME REVISION UPDATED STATUS CHART NAMESPACE r04bac65d2f 1 Mon Feb 11 14:51:08 2019 DEPLOYED dynamic-gateway-service-1.0.16 apiconnect r1001d56a76 1 Mon Feb 11 14:50:46 2019 DEPLOYED apic-analytics-2.0.0 apiconnect r14613f8fca 1 Mon Feb 11 14:50:26 2019 DEPLOYED apic-portal-2.0.0 apiconnect raeb5658fc0 1 Mon Feb 11 14:51:27 2019 DEPLOYED dynamic-gateway-service-1.0.16 apiconnect rbcb2382b5e 1 Mon Feb 11 14:50:06 2019 DEPLOYED apiconnect-2.0.0 apiconnect rf19e62b277 1 Mon Feb 11 14:50:03 2019 DEPLOYED cassandra-operator-1.0.0 apiconnect - Use the following command to delete the replicasets for that release in its namespace:
kubectl delete rs -n <namespace> -l release=<release_name>For example, using the previous sample output:
kubectl delete rs -n apiconnect -l release=rbcb2382b5e
- Find the Helm release name and namespace for the subsystem that you are switching to dev
mode:
- To review your installation mode, use
apicup subsys get <subsystem_name>.For example,
apicup subsys get mgmt:Kubernetes settings =================== Name Value Errors ---- ----- ------ . . mode dev . .