./cloudcore --minconfig # With --minconfig , you can easily used this configurations as reference. # It's useful to users who are new to KubeEdge, and you can modify/create your own configs accordingly. # This configuration is suitable for beginners.
./cloudcore --defaultconfig # With --defaultconfig flag, users can easily get a default full config file as reference, with all fields (and field descriptions) included and default values set. # Users can modify/create their own configs accordingly as reference. # Because it is a full configuration, it is more suitable for advanced users.
$ ./edgecore --minconfig 2020-02-18 22:51:09.753952 I | INFO: Install client plugin, protocol: rest 2020-02-18 22:51:09.780037 I | INFO: Installed service discovery plugin: edge I0218 22:51:10.063748 873 util.go:395] Looking for default routes with IPv4 addresses I0218 22:51:10.063875 873 util.go:400] Default route transits interface "enp0s3" I0218 22:51:10.109175 873 util.go:209] Interface enp0s3 is up I0218 22:51:10.111900 873 util.go:257] Interface "enp0s3" has 2 addresses :[172.18.18.10/16 fe80::a2d:57ce:28ba:4290/64]. I0218 22:51:10.119191 873 util.go:225] Checking addr 172.18.18.10/16. I0218 22:51:10.119314 873 util.go:232] IP found 172.18.18.10 I0218 22:51:10.126894 873 util.go:263] Found valid IPv4 address 172.18.18.10 for interface "enp0s3". I0218 22:51:10.126980 873 util.go:406] Found active IP 172.18.18.10 # With --minconfig , you can easily used this configurations as reference. # It's useful to users who are new to KubeEdge, and you can modify/create your own configs accordingly. # This configuration is suitable for beginners.
./edgecore --defaultconfig 2020-02-18 22:54:25.586421 I | INFO: Install client plugin, protocol: rest 2020-02-18 22:54:25.587414 I | INFO: Installed service discovery plugin: edge I0218 22:54:25.588917 887 util.go:395] Looking for default routes with IPv4 addresses I0218 22:54:25.589682 887 util.go:400] Default route transits interface "enp0s3" I0218 22:54:25.591263 887 util.go:209] Interface enp0s3 is up I0218 22:54:25.591991 887 util.go:257] Interface "enp0s3" has 2 addresses :[172.18.18.10/16 fe80::a2d:57ce:28ba:4290/64]. I0218 22:54:25.593474 887 util.go:225] Checking addr 172.18.18.10/16. I0218 22:54:25.593883 887 util.go:232] IP found 172.18.18.10 I0218 22:54:25.594312 887 util.go:263] Found valid IPv4 address 172.18.18.10 for interface "enp0s3". I0218 22:54:25.594539 887 util.go:406] Found active IP 172.18.18.10 I0218 22:54:25.613268 887 util.go:395] Looking for default routes with IPv4 addresses I0218 22:54:25.613309 887 util.go:400] Default route transits interface "enp0s3" I0218 22:54:25.613599 887 util.go:209] Interface enp0s3 is up I0218 22:54:25.613761 887 util.go:257] Interface "enp0s3" has 2 addresses :[172.18.18.10/16 fe80::a2d:57ce:28ba:4290/64]. I0218 22:54:25.613818 887 util.go:225] Checking addr 172.18.18.10/16. I0218 22:54:25.613845 887 util.go:232] IP found 172.18.18.10 I0218 22:54:25.613867 887 util.go:263] Found valid IPv4 address 172.18.18.10 for interface "enp0s3". I0218 22:54:25.613884 887 util.go:406] Found active IP 172.18.18.10 # With --defaultconfig flag, users can easily get a default full config file as reference, with all fields (and field descriptions) included and default values set. # Users can modify/create their own configs accordingly as reference. # Because it is a full configuration, it is more suitable for advanced users.