There are a couple quick changes you can do to your current YAML file to make them 1.3.0 compatible if you are using the 1.2.x standard.
spectop level keys.
camelCase. Regarding abbreviations, follow these examples:
# Vanilla and Kubernetes Controllers shown for example controllers: - name: Controller-1 user: serge host: 184.108.40.206 keyfile: ~/.ssh/id_rsa iofoguser: name: Quick surname: Start email: firstname.lastname@example.org password: q1u45ic9kst563art - name: Controller-2 kubeconfig: ~/.kube/config iofoguser: name: Quick surname: Start email: email@example.com password: q1u45ic9kst563art agents: - name: Agent-1 user: serge host: 220.127.116.11 keyfile: ~/.ssh/id_rsa
--- apiVersion: iofog.org/v1 kind: ControlPlane metadata: name: any namespace: default spec: iofogUser: name: iofog surname: user email: firstname.lastname@example.org password: 89ghuiwfg80 # 3 types of controllers shown for example only controllers: - name: vanilla host: 18.104.22.168 ssh: user: default keyFile: ~/.ssh/id_rsa - name: kubernetes kube: config: ~/.kube/config - name: local host: localhost --- apiVersion: iofog.org/v1 kind: Connector metadata: name: vanilla namespace: default spec: host: 22.214.171.124 ssh: user: connector keyfile: ~/.ssh/id_rsa --- apiVersion: iofog.org/v1 kind: Connector metadata: name: kubernetes namespace: default spec: kube: config: ~/.kube/config --- apiVersion: iofog.org/v1 kind: Agent metadata: name: agent-name namespace: default spec: host: 126.96.36.199 ssh: user: agent keyFile: ~/.ssh/id_rsa
Note: we separate kinds by three dashes, this allows you to use a single file, to deploy all your infrastructure and keep it legible.
As you can see, the top fields are now standard for whatever you want to deploy, which you simply identify in the
The name and namespaces you were operating in are now handled under the metadata tag, and the spec tag, while different for each kind, contains
the same kind of data as the previous spec, simply under spec. Our current YAML spec version is 1, but may be updated in the future.
This also carries over to your microservices. If you wish to deploy your services through iofogctl, you can move these over very easily by adding the following to the top of your deployment file for each application that file containers:
apiVersion: iofog.org/v1 kind: Application metadata: name: 'old-resource-name' spec:
and simply move the microservices and routes sections from 1.2.x under spec. Take care to use the new
kube fields also.