e3b444c912
And, while we are it, clean up DNSZone so that it has separate notions of TaskName, DNSName and HostedZoneID. We conflated the three previously, which we don't want to do at the task layer. We don't want to conflate the TaskName and the DNSName so that we can create a private & public hosted zone with the same DNSName. We don't want to "smuggle" the hosted zone ID in the DNSName because it doesn't belong in the task layer. Fix #1374 |
||
|---|---|---|
| .. | ||
| cloudup | ||
| fitasks | ||
| k8sapi | ||
| loader | ||
| nodeup | ||
| secrets | ||
| utils | ||
| README.md | ||
| assetstore.go | ||
| ca.go | ||
| changes.go | ||
| cloud.go | ||
| compare_with_id.go | ||
| context.go | ||
| default_methods.go | ||
| deletions.go | ||
| dryrun_target.go | ||
| errors.go | ||
| executor.go | ||
| files.go | ||
| has_address.go | ||
| http.go | ||
| named.go | ||
| resources.go | ||
| secrets.go | ||
| target.go | ||
| task.go | ||
| timestamp.go | ||
| topological_sort.go | ||
| users.go | ||
| values.go | ||
| vfs_castore.go | ||
| vfs_castore_test.go | ||
README.md
fi - Fast Install
The fi package is responsible for holding the infrastructure that supports installing, provisioning and deploying resources to get kubernetes running in a cloud.
Cloudup
The cloudup package within fi contains infrastructure that handles deploying cloud resources.
Cloudup has a concept of models. These are a core component of kops, and critical to understanding how the tool works. They offer flexibility for the tool, and serve as the main representation of infrastructure in the cloud. They are the glue that will map resources to kops functionality. These models are stored in upup/models/cloudup.
AWS
Currently aws is the most verbose and feature rich of the 2 primarily supported cloud providers. Cloudup will handle reading the aws models (found in _aws) and apply these resources to the cloud.
A user will notice awstasks and awsup directores within cloudup. These are the files that will actually map an aws resource (API Request) to go code.
By convention, every used API request in kops for aws, has an associated awstask with it.
GCE
Nodeup
This tool is secondary to cloudup.
After the resources to the cloud have been deployed, we will now need to provision the resources.
Nodeup runs as a binary on VMs in the cloud and will handle bringing up a kubernetes cluster.
The core bits of nodeup infrastructure can be found here.