| 1234567891011121314151617181920212223242526 |
- ## This is the service-wise list of constructs that need to be handled specially.
- Please refer https://rancher.com/docs/rancher/v2.x/en/v1.6-migration/ to transition these to Rancher 2.0.
- gogs:
- labels:
- >>io.rancher.container.pull_image
- links:
- Refer: https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/
- Please add the necessary Service Discovery Records for your Rancher 2.0 Kubernetes workload to implement the links.
- ports:
- Refer: https://rancher.com/blog/2018/2018-08-14-expose-and-monitor-workloads/
- Please add a hostPort or a nodePort to your Kubernetes workload to expose the ports used.
- scale:
- start_on_create:
- volumes:
- postgres:
- labels:
- >>io.rancher.container.pull_image
- scale:
- start_on_create:
- volumes:
- ## More Docker/Rancher1.6 constructs that need to be transitioned to Kubernetes/Rancher 2.0 in a special way:
- Rancher Metadata - Incase your applications depend on metadata.
- Rancher 1.6 FQDN resolution format
- Please contact Rancher Support for more help to migrate these to Rancher 2.0, as there is no direct translation available.
|
