Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions Documentation/dev/node-bootstrap-flow.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,6 @@ Additionally, only on one of the master nodes the following kubernetes bootstrap
* `bootkube.service` deploys the initial bootstrapping control-plane. It is started only after `kubelet.service` _is started_. It is a oneshot unit and cannot crash, and it runs only during bootstrap
* `tectonic.service` deploys tectonic control-plane. It is started only after `bootkube.service` _has completed_. It is a oneshot unit and cannot crash, and it runs only during bootstrap

[tectonic-torcx]: https://github.com/coreos/tectonic-torcx

## Service ordering

Service ordering is enforced via systemd dependencies. This is the rationale for the settings, with relevant snippets:
Expand Down
6 changes: 0 additions & 6 deletions modules/ignition/variables.tf
Original file line number Diff line number Diff line change
Expand Up @@ -45,12 +45,6 @@ variable "cloud_provider_config" {
default = ""
}

variable "torcx_store_url" {
type = "string"
description = "(optional) URL template for torcx store. Leave empty to use the default CoreOS endpoint."
default = ""
}

variable "etcd_count" {
type = "string"
default = 0
Expand Down